Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow setting global enum naming strategy similar to property naming strategy #4674

Closed
hajdamak opened this issue Aug 19, 2024 · 1 comment
Closed

Allow setting global enum naming strategy similar to property naming strategy #4674

hajdamak opened this issue Aug 19, 2024 · 1 comment
Labels
2.19 Issues planned at 2.19 or later
Milestone
2.19.0

Comments

@hajdamak
Copy link

Is your feature request related to a problem? Please describe.

  • Currently you have to annotate all enums with EnumNaming in order to change default enum naming strategy which is cumbersome and verbose.

Describe the solution you'd like

It should be possible to set default enum naming strategy directly on ObjectMapper.

Usage example

ojbectMapper.setEnumNamingStrategy(EnumNamingStrategies.CAMEL_CASE)

Additional context

No response
@hajdamak hajdamak added the to-evaluate Issue that has been received but not yet evaluated label Aug 19, 2024
@cowtowncoder
Copy link
Member

Sounds reasonable. PR would be most welcome.

@cowtowncoder cowtowncoder added pr-welcome Issue for which progress most likely if someone submits a Pull Request and removed to-evaluate Issue that has been received but not yet evaluated labels Aug 21, 2024
@badoken badoken mentioned this issue Sep 25, 2024
Closed
@cowtowncoder cowtowncoder added the 2.19 Issues planned at 2.19 or later label Sep 25, 2024
@badoken badoken mentioned this issue Sep 29, 2024
Merged
@cowtowncoder cowtowncoder removed the pr-welcome Issue for which progress most likely if someone submits a Pull Request label Oct 3, 2024
@cowtowncoder cowtowncoder added this to the 2.19.0 milestone Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2.19 Issues planned at 2.19 or later
Projects
None yet
Milestone
2.19.0
Development

No branches or pull requests
2 participants
@cowtowncoder @hajdamak