New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Duplicate schema names exported #205
Comments
@brianbolnick thanks for repoting the issue, can you please provide a complete schema if possible so i can run it on my end? |
@brianbolnick I changed the generation of imports in barrel files to use Set instead of array to prevent duplicate imports. Can you please check if this solves your problem or if it generates problems in other places of the schemas. Please also be aware that the latest version is targeted for the use with Also zod 3.21.4 might make problems because of a type error in the schemas that happens in |
Looks like it is still occurring with the current versions of prisma and zod, unfortunately. I'll try to revert back where possible, but may need to figure something else out until it's all fully supported :) |
Well, that's odd. Is it possible to provide the full schema so I can reproduce the issue on my end? |
Unfortunately it's a private repo and I can't share it :/ It's only affecting one model, so I'll see if I can put together a replica of it and any relations to it that you could use later. |
Describe the bug
Hi! Love the concept behind this repo. Just ran my first generate and it has a duplicate schema exported. I've tried with both single and multi-file outputs. The multi-file has seemed to shed some possible light. Wondering if it has anything to do with a double export 🤷:
Which leads to the index file including both of these:
It only happened with this one model, so it very likely could be an issue on our end. Here's the schema itself:
Screenshots
N/A
Package versions (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: