-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate _count as always nullable:true #130
Comments
There is no such option. For what kind of generated class it should be null (model, input)? |
Ref: #84 |
The problem with the _count property is, that it is automatically generated per default as nullable: false, but the default way of using prisma doesn't include the _count property meaning I always have to include it, which is counterintuitive to using prisma. |
I dont understand the problem. If you have graphql client error about count property, it means that you must provide it. Using prisma for getting count is not supposing to return null. |
How can i delete this field?, since this field its not in the type definition on the prisma client type as a part of the model. |
@denes16
See https://github.com/unlight/prisma-nestjs-graphql#decorate |
how to delete this field from generation or how can I add isAbstract in every @ObjectType({ isAbstract: true }) |
Is it possible to generate the _count property as always { nullable:true }? I couldn't find the generator option to do that.
The text was updated successfully, but these errors were encountered: