0.16.1

Changelog

1. The supported Prisma version has been bumped to v3.1.1 🚀
   There was no changes in DMMF thus no changes in generated code blocks this time.

2. Prisma version check error message has been improved 💪
   Now it prints more descriptive message about the versions missmatch, eg.:

   Error: Looks like an incorrect version "3.1.1" of the Prisma packages has been installed. 
   'typegraphql-prisma' works only with selected versions, so please ensure
   that you have installed a version of Prisma that meets the requirement: "~3.0.1".
   Find out more about that requirement in docs:
   https://prisma.typegraphql.com/docs/basics/prisma-version
   

   And points to the docs website, where it's described why it behaves like that and how to couple with it:
   https://prisma.typegraphql.com/docs/basics/prisma-version

0.16.0

Changelog

1. The supported Prisma version has been bumped to the newest major release, v3.0.1 🚀
   This means that all the features hidden behind the preview feature flags, like orderByRelation or selectRelationCount is now automatically emitted. Because of that, expect plenty of changes in the generated schema, like _count fields or new sort inputs.

2. Base support for omiting input type field has been added 💪
   So you can now provide the input: true option to @TypeGraphQL.omit:

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

   So that the field won't show anymore in all model-related input types, like UserCreateInput:

   input UserCreateInput {
     email: String!
     posts: PostCreateManyWithoutAuthorInput!
   }

0.15.0

Changelog

1. Supported Prisma version has been bumped to v2.30.
   This means that the fullTextSearch preview feature is also supported 🚀

2. In some rare cases when original model name is a substring of new type name (like User -> MainUser), it resulted in duplicated suffix/prefix names (like MainMainUser) - see #158.
   Now the issue is no longer present since this relase 💪

3. Added emitIdAsIDType generator config option, which emits model id fields as ID scalar for GraphQL type (#26).

4. In previous version, _count field for model type was always emitted, even when selectRelationCount Prisma preview feature was not enabled. That behavior was leading to runtime Prisma error because it was trying to translate selected _count query fields into Prisma Client args.

   Since this release, _count field are available only when you do enable the selectRelationCount preview feature. If not, the generated model type classes won't have that field, as well as CRUD resolvers methods body will not contain logic for supporting that.

0.14.8

Changelog

1. Supported Prisma version has been bumped to 2.29 🚀

2. namedConstraints preview flag is now supported, so you can rename your compound primary keys or unique constraints 💪

0.14.7

Changelog

1. Supported Prisma version has been bumped to v2.27.

   This release does not contain any significant changed in DMMF thus no changes, fixes or features added this time.
   All the focus is shift on the website: https://prisma.typegraphql.com/

0.14.6

Changelog

1. Support for filterJson preview feature (released in Prisma 2.23) has been now added 🚀

0.14.5

Changelog

1. Supported Prisma version has been bumped to v2.26.
   This release does not contain any significant changed in DMMF thus no changes, fixes or features added this time.

0.14.4

Changelog

1. Supported Prisma version has been bumped to v2.25. This release does not contain any changed in DMMF thus no changes, fixes or features added this time.

2. Support for filterJson preview feature (released in Prisma 2.23) will be added soon. Stay tuned! 📻

0.14.3

Changelog

1. This release is compatible with the newest Prisma v2.23 🚀
   This means that now all the aggregation-related fields like avg or count has been renamed to the _ prefix: _avg, _count, etc.

   This was breaking change for "options in groupBy queries" but typegraphql-prisma goes further and change it for all the types, according to the deprecations in DMMF. So please be aware of this changes and update your client's queries.

2. The AggregateOutputType nullability issue has been fixed on Prisma's side, so be aware that now array fields of aggregate types are nullable.

3. The filterJson preview feature is not yet supported. Stay tuned! 📻

0.14.2

Changelog

This is a hotfix release, caused by a branching issue on git.
It only adds support for proper naming of XYZAvgOrderByAggregateInput and others inputs used by orderByAggregateGroup preview feature.
Now the model name part prefix should be correctly renamed when you use @@TypeGraphQL.type(name: "...") directive comment:

- export class UserSumOrderByAggregateInput {
+ export class ClientSumOrderByAggregateInput {