Roman Vasilev
Roman Vasilev
Looks normal and it works for me. Are you using standard set of tools like tsc compiler, reflect-metadata, etc? Or non-standard, like swc/esbuild, lite reflection lib?
Sorry, but I dont have any ideas why it's not working. Can you provide minimal repository to reproduce error?
I think problem in `whitelist = true`. But it does not make sense to use whitelist = true with graphql, graphql is typed. I think you have some options here:...
There is an issue related to typescript when trying compare big models with recursion, if you are brave to patch typescript try this solution https://github.com/unlight/prisma-nestjs-graphql/issues/65#issuecomment-994742228
There is no such option. For what kind of generated class it should be null (model, input)? What is corresponding prisma expression which returns null instead of number?
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...
No, it's not possible.
By doing some configuration - no possible, data for fields is coming from Prisma. All fields are optional in `*UpdateInput` types.
It was not designed for that. But people are saying that they adopted it somehow, probably with some modification of result generated classes.