-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Case insensitive enum deserialization feature #1313
Comments
Sounds like possibly something to support, even thought it sort of goes against grain of JSON which is case-sensitive. Not 100% sure what the best way is, since use of |
+1 |
@cowtowncoder I'd like to help you fix it. Can I have permission to create a branch? |
@AnaEliza the usual way is to do a fork, for which you do not need extra access. |
Issue #1313: New IgnoreCase feature to deserialize enums
Fixed via #1520. |
…rty allowance (or not) of case-insensitivity
Enums are only properly deserialized if the value is uppercase. We don't want to force all clients to have to manipulate their data into uppercase, so we would like to accept a String case-insensitively and have it be deserialized into the correct enum.
Others have encountered this issue and there are various solutions for achieving this effect.
I think this feature is used often enough that it warrants being added to the core, so that we could simply do something like:
Instead of having to search up the solution each time we encounter this issue.
The text was updated successfully, but these errors were encountered: