0.20.4

Changelog

1. The supported Prisma version has been bumped to v3.15.0 💪
2. Because of small changes in DMMF for MongoDB models, you can expect changes in the order of fields in generated classes.
   No breaking changes or changes affecting usability detected.

0.20.3

Changelog

1. The supported Prisma version has been bumped to v3.14.0 💪
   No changes in DMMF, so you can safely upgrade without any changes in generated code.

0.20.2

Changelog

1. The supported Prisma version has been bumped to v3.13.0 💪
   No changes in DMMF, so you can safely upgrade without any changes in generated code.

2. Stay tuned for more new features! 📻

0.20.1

Changelog

1. Added support for providing custom key of GraphQL context, where the Prisma Client can be found:

   generator typegraphql {
     provider         = "typegraphql-prisma"
     contextPrismaKey = "customPrisma"
   }

   Thanks to this generator option, all the generated resolvers will try to use the Prisma Client from context["customPrisma"] instead of the standard context.prisma.
   This may help in some cases, like when you have multiple Prisma schemas with separate clients generated.
   https://prisma.typegraphql.com/docs/advanced/custom-prisma-context-key

0.20.0

Changelog

1. The supported Prisma version has been bumped to v3.12.0.
   No changes in DMMF, so you can safely upgrade without any changes in generated code.

2. Support for embedded documents for MongoDB has been added 🚀
   Now you can safely use type keyword in your schema and read the nested data by your queries:

   model User {
     id      String      @id @default(auto()) @map("_id") @db.ObjectId
     email   String      @unique
     age     Int?
     address UserAddress
   }
   
   type UserAddress {
     street String
     number Int?
     city   String
   }

   query GetUsersWithAddress {
     users {
       id
       email
       age
       address {
         city
         number
         street
       }
     }
   }

      {
     "data": {
       "users": [
         {
           "id": "624d5468d0cadcc837fca368",
           "email": "[email protected]",
           "age": 55,
           "address": {
             "city": "Los Angeles",
             "number": null,
             "street": "5th Avenue"
           }
         }
       ]
     }
   }

0.19.2

Changelog

1. The supported Prisma version has been bumped to v3.11.0.
   No changes in DMMF, so you can safely upgrade without any changes in generated code.

2. Support for embedded documents for MongoDB is in progress 🚧 You can expect that in the next release 👀

0.19.1

Changelog

1. The supported Prisma version has been bumped to v3.10.0.
   You can expect some small tweaks due to changes in DMMF, like different order of fields in input types.

2. Support for embedded documents for MongoDB will be added soon ⌚ Stay tuned!

0.19.0

Changelog

1. Support for more granular setting of hiding field in input types has been added 🚀
   Now you can select input kinds by passing an array to the /// @TypeGraphQL.omit option:

   model User {
     id        Int     @default(autoincrement()) @id
     email     String  @unique
     /// @TypeGraphQL.omit(input: ["update", "where", "orderBy"])
     password  String
     posts     Post[]
   }

   This way the field will be hidden only in selected kind of input types, like UserUpdateInput or UserWhereInput but not UserCreateManyInput.
   The available options are: "create","update", "where" and "orderBy".

0.18.5

Changelog

1. The supported Prisma version has been bumped to v3.9.2.
   No breaking changes in the schema is expected, so you can safely upgrade.

2. Stay tuned for more as the new feature with more granular input omit options is coming soon 👀

0.18.4

Changelog

1. This release only bumps the supported Prisma version to v3.8.0.
   However, due to some Prisma issue, you may need to add a fs-jetpack dependency to your project as a temporary workaround.
   The alternative solution is to make sure you have installed patched Prisma version v3.8.1.

2. Stay tuned for more features 🚀