Skip to content

Move Enum-related DeserializationFeatures into EnumFeature (3.0) #5079

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

Closed
cowtowncoder opened this issue Apr 9, 2025 · 0 comments · Fixed by #5088
Closed

Move Enum-related DeserializationFeatures into EnumFeature (3.0) #5079

cowtowncoder opened this issue Apr 9, 2025 · 0 comments · Fixed by #5088
Labels
3.0-release-notes Issues relevant for 3.0 release notes. 3.0 Issue planned for initial 3.0 release enum Related to handling of Enum values
Milestone

Comments

@cowtowncoder
Copy link
Member

There are some DeserializationFeatures that would make more sense as more specific EnumFeatures. Let's make them. This includes:

  • FAIL_ON_NUMBERS_FOR_ENUMS (default: false)
  • READ_ENUMS_USING_TO_STRING (default: true, was false in 2.x)
  • READ_UNKNOWN_ENUM_VALUES_AS_NULL (default: false)
  • READ_UNKNOWN_ENUM_VALUES_USING_DEFAULT_VALUE (default: false)
@cowtowncoder cowtowncoder added enum Related to handling of Enum values 3.0 Issue planned for initial 3.0 release 3.0-release-notes Issues relevant for 3.0 release notes. labels Apr 9, 2025
@cowtowncoder cowtowncoder added this to the 3.0.0-rc3 milestone Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-release-notes Issues relevant for 3.0 release notes. 3.0 Issue planned for initial 3.0 release enum Related to handling of Enum values
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant