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

Add a new property in @JsonNaming to allow override of explicit property names #926

Open
cowtowncoder opened this issue Sep 10, 2015 · 1 comment
Open

Add a new property in @JsonNaming to allow override of explicit property names #926

cowtowncoder opened this issue Sep 10, 2015 · 1 comment

Comments

@cowtowncoder
Copy link
Member

(note: follow-up to #918 which allows changing of global defaults for whether explicitly named properties are renamed by naming strategy)

It would make sense to add a new property in @JsonNaming to allow for specifying whether explicitly named properties (using @JsonProperty or other annotations) should still be renamed using PropertyNamingStrategy or not.

Note: value of property should be OptBoolean, to allow for tri-state choice (not just 'true', 'false' but also 'just use global default`).
@cowtowncoder cowtowncoder mentioned this issue Sep 10, 2015
Merged
@cowtowncoder cowtowncoder mentioned this issue Jan 13, 2016
Closed
@cowtowncoder cowtowncoder changed the title Add a new property in @JsonNaming to allow override of explicit property names (2.8) Add a new property in @JsonNaming to allow override of explicit property names Feb 12, 2016
@cowtowncoder cowtowncoder added this to the 2.7.0 milestone Apr 22, 2016
@cowtowncoder cowtowncoder changed the title (2.8) Add a new property in @JsonNaming to allow override of explicit property names Add a new property in @JsonNaming to allow override of explicit property names Apr 22, 2016
@cowtowncoder cowtowncoder changed the title Add a new property in @JsonNaming to allow override of explicit property names (2.8) Add a new property in @JsonNaming to allow override of explicit property names Apr 22, 2016
@cowtowncoder cowtowncoder removed this from the 2.7.0 milestone May 5, 2016
@cowtowncoder cowtowncoder changed the title (2.8) Add a new property in @JsonNaming to allow override of explicit property names Add a new property in @JsonNaming to allow override of explicit property names May 5, 2016
@cowtowncoder cowtowncoder removed the 2.8 label May 20, 2016
@cowtowncoder
Copy link
Member Author

Requires changes to AnnotationIntrospector because currently only Class (of PropertyNamingStrategy) is needed. Not sure what'd be the best way; could create separate Value object (one possibility), or pass MapperConfig<?> in to allow construction from within introspector.
Or alternatively completely new method... none of which seems exactly optimal from all perspectives, including backwards-compatibility.

@cowtowncoder cowtowncoder added 2.10 and removed 2.9 labels Jul 17, 2018
@cowtowncoder cowtowncoder added 2.12 and removed 2.10 labels Apr 3, 2020
@cowtowncoder cowtowncoder added 2.13 and removed 2.12 labels Oct 27, 2020
@cowtowncoder cowtowncoder removed the 2.13 label Feb 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cowtowncoder