[Prisma plugin] Required field should be non-nullable automatically unless we override it about pothos HOT 2 OPEN

We might be able to add that as a setting., but this is intentional.

Pothos v4 made changes so that you will now see type-errors if you try to make a nullable field in your db non-nullable in the GraphQL.

Pothos is designed to never rely on the shape of your data to determine the shape of the GraphQL schema. This means that a change in your DB (or other data) should never automatically change the GraphQL schema. This abstraction is critical for making it manageable to maintain large APIs and has worked out really well in the projects I've worked on. It does require adding some extra definitions for which fields are nullable, but to me this is a worthwhile tradeoff.

But, if it seems worth it to you, we could add a setting to the builder that enables mirroring the Schemas nullability

from pothos.

The setting to enable mirroring the schema’s nullability would be perfectly helpful for me. I’m eager to see this feature come to fruition, and I’m available to assist if needed!

from pothos.