chrishoermann

Well, that's odd. Is it possible to provide the full schema so I can reproduce the issue on my end?

@clabnet yes the schemas you mentioned can be used for CRUD operations. I personally use it with `trpc` but have not used it with `swagger` or `fastify` In your example...

@jaschaephraim thanks for the report. I looked into it a bit and I'm not quite sure why prisma did it this way. Because when inspecting the prisma type `JsonValue` it...

I found [an issue in the prisma repo](https://github.com/prisma/prisma/issues/12689) that is about the behaviour I mentioned and it seems that json fields can contain `null` when beeing retrieved from the database....

@jaschaephraim in `v3.0.0` I revamped the json implementation so it exactly matches the types generated by prisma. for a given model like ```prisma model JsonModel { id Int @id @default(autoincrement())...

@jamespsterling for this type error to go away you have to set `strictNullChecks: true` in your `tsconfig.json`.

@julimancan have you been able to fix this issue? if not can you provide your (simple) schema? in the screenshot it looks like there is a newer version of prisma...

@kevin-dp If I understand this correctly you'd suggest that we capitalize the first letter in each model regardless of the casing of the actual model? This would definitely be possible...

@fotoflo @kevin-dp - Have you tried using uppercase in your model names to see if the error persists? - sometimes deleting the `node_modules` or the generated prisma client folder also...

@ksdaylight Thanks for reaching out. Since I do not use MongoDB in any of my projects I don't have real usecases. It would be nice if you can provide a...