You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My API project uses TypeGraphQL to generate its schema from Prisma/Resolvers.
In TypeGraphQL, the way you control which fields of each Prisma model get included in the generated GraphQL models is by using a description annotation like: /// @TypeGraphQL.omit(input: true, output: true)
When generating json-schema using this library, we see descriptions on models like so:
@mmmeff Do you have a friendly solution in mind? Like defining an ignoreComment field, which might accept a list of strings, and the description will be omitted as soon as the string is detected? Do you think this would work for your needs?
My API project uses TypeGraphQL to generate its schema from Prisma/Resolvers.
In TypeGraphQL, the way you control which fields of each Prisma model get included in the generated GraphQL models is by using a description annotation like:
/// @TypeGraphQL.omit(input: true, output: true)
When generating json-schema using this library, we see descriptions on models like so:
It would be great if I could add a pattern to omit descriptions in the generated json-schema or at least disable them outright.
The text was updated successfully, but these errors were encountered: