-
-
Notifications
You must be signed in to change notification settings - Fork 51
TypeError for default values when using enums #640
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
Comments
I've opened a PR for this issue: #636 |
This is not an edge case. I'm stuck with version 0.12.1 because the default values generation for zod is broken. |
@AndKiel Glad to know we're not the only one! 🙂 |
same thing here |
I merged the contents of PR #636, will release it as soon as the README is fixed |
I just published v0.16.0 which is included this fix. |
For those on this thread, I noticed that this effort introduced a bug with underscore transformation. Since then, I've opened #828 |
The latest of this wonderful plugin has unfortunately broken default values for us regarding the default stringified values. I'm unsure if others are having this issue as it's very new, and this could very well be an edge-case.
Related PR: #529
The Problem
For example, if one were to have the following enum:
We then have the generated schema:
This would throw the following type errors:
Output of Solution
Adding this fix/feature generates this output:
I think having a flag to specify enum types' respective paths as their default values as well as a naming convention (since that can be changed) configuration, we should be able to address it.
The text was updated successfully, but these errors were encountered: