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
Is your feature request related to a problem? Please describe.
I'm using zod-prisma-types to generate Zod schemas from my Prisma models, but I don't need the TypeScript types that are also generated. This leads to unnecessary duplicate types in project as prisma client also export the types itself.
Describe the solution you'd like
I would like an option (e.g., a CLI flag or config setting) to disable only the TypeScript type generation while still generating the Zod schemas.
Describe alternatives you've considered
I am using the zod-prisma library instead for generating schemas, but I prefer the approach provided by zod-prisma-types and would like to use it without the extra TypeScript types.
Additional context
If there's already a way to achieve this, could you provide guidance on how to do it? If not, would it be possible to add this feature in a future update?
Thanks for the awesome library! 🚀
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm using zod-prisma-types to generate Zod schemas from my Prisma models, but I don't need the TypeScript types that are also generated. This leads to unnecessary duplicate types in project as prisma client also export the types itself.
Describe the solution you'd like
I would like an option (e.g., a CLI flag or config setting) to disable only the TypeScript type generation while still generating the Zod schemas.
Describe alternatives you've considered
I am using the zod-prisma library instead for generating schemas, but I prefer the approach provided by zod-prisma-types and would like to use it without the extra TypeScript types.
Additional context
If there's already a way to achieve this, could you provide guidance on how to do it? If not, would it be possible to add this feature in a future update?
Thanks for the awesome library! 🚀
The text was updated successfully, but these errors were encountered: