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.

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

Use @JsonProperty over EnumNamingStrategy for Enum serialization #4040

Merged

Conversation

iProdigy
Copy link
Contributor

Serialization complement of #4037

if (name == null) {
name = namingStrategy.convertEnumToExternalName(enumValue.name());
}
textual[i] = config.compileString(name);
Copy link
Contributor Author

@iProdigy iProdigy Jul 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
textual[i] = config.compileString(name);
if (config.isEnabled(EnumFeature.WRITE_ENUMS_TO_LOWERCASE)) {
name = name.toLowerCase();
}
textual[i] = config.compileString(name);

Should WRITE_ENUMS_TO_LOWERCASE apply here? (my opinion is no when naming strategy is used... however @JsonProperty is lowercased in constructFromName)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depends on how PropertyNamingStategy version does it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is a lowercase SerializationFeature for the general case

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct: lower-casing is datatype-specific, no SerializationFeature (nor will there ever be).

The main question is interesting one; I can see arguments either way.
I think that since EnumFeature.WRITE_ENUMS_TO_LOWERCASE is slightly more dynamic (Enum naming strategy being defined as annotations in class definition or mix-in), it should have precedence and, when enabled, force lower-casing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I think code as-is does what is my leaning. Great!

Copy link
Contributor Author

@iProdigy iProdigy Jul 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cowtowncoder the current code doesn't force lower-casing, I think you're looking at the suggested diff

Edit: created a PR for this - if I misunderstood your comment, feel free to close it

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iProdigy Ok I must have thought suggestion was applied and not looked at actual change. Thank you for following through, I just merged follow-up PR!

@cowtowncoder cowtowncoder merged commit 26f56ff into FasterXML:2.16 Jul 16, 2023
3 checks passed
@cowtowncoder cowtowncoder changed the title feat(ser): use JsonProperty over EnumNamingStrategy Use @JsonProperty over EnumNamingStrategy for Enum serialization Jul 16, 2023
cowtowncoder added a commit that referenced this pull request Jul 16, 2023
@iProdigy iProdigy deleted the fix/enum-naming-override-property branch July 16, 2023 00:19
@cowtowncoder
Copy link
Member

Thank you again @iProdigy for this and other PRs! 2.16 will have much improved handling thanks to these fixes, as well as earlier work by @JooHyukKim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants