-
Notifications
You must be signed in to change notification settings - Fork 136
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
Deserialisation of enums does not respect ordering #117
Milestone
Comments
tapina
added a commit
to cambridgeweblab/jackson-module-jsonSchema
that referenced
this issue
Oct 17, 2016
Seems reasonable to improve this to keep ordering. |
I created a PR with the test and the (one liner) fix. |
Thank you -- I applied the fix for 2.8(.5). |
nealeu
added a commit
to cambridgeweblab/common-java
that referenced
this issue
Nov 10, 2021
…hat we had on forks The last is the enum -> class issues that was rejected: cambridgeweblab/jackson-databind@54a988a Included are: FasterXML/jackson-module-jsonSchema#117 FasterXML/jackson-module-jsonSchema#112 FasterXML/jackson-module-jsonSchema@8aae855
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Deserialisation of enums is to a Set field on ValueTypeSchema. This is created as a HashSet which leads to unpredictable ordering. Here is a (failing) test case:
The text was updated successfully, but these errors were encountered: