-
Notifications
You must be signed in to change notification settings - Fork 66
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
Support unexpected values in Enums #692
Comments
Feel free to experiment, @brice-laurencin. I'm curious about this use case since it's somewhat common. In my experience, usually the server would change the API to a new version e.g. Changing the main version to not be compatible smells and it's an anti-pattern. So I'm not sure how much resources we should spend on this. |
@ricardozanini @hbelmiro This is being labeled as Stale. |
If the server evolves and adds (or, God forbid, deletes) entries in an enum, the client will likely fail hard.
It'd be interesting to add a default
UNEXPECTED
value in all the generated enum, this one being the default value when parsing fails.I can try to cook a PR for this, if you think that's a sensible idea.
The text was updated successfully, but these errors were encountered: