-
Notifications
You must be signed in to change notification settings - Fork 85
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
Advise on "open enums" #26
Comments
I think this is more a question for JSON schemas. I think the "right" way is to use a choice, either a "closed" enum or an open string for future values: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a part of our json schema which prescribes values based on what's supported now. ex.
However, if we added another value later, we would want old code to not fail. Right now enums are validated by default.. We still want to know what the constants should be... Any advise?
The text was updated successfully, but these errors were encountered: