Detect when camel case properties are used for a class that's configured to use snake case #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If a class is configured with
@JsonNaming(PropertyNamingStrategy.SnakeCaseStrategy.class)
but one of its@JsonProperty
annotations uses camel case, the property is serialized using the camel case strategy i.e. the@JsonProperty
annotation overrides the configured naming strategy. This behaviour leads to unexpected results because you would assume that Jackson would always use the configured naming strategy.This PR updates
com.nosto.beanie.AbstractJacksonBeanTest#namingStrategy
to detect when a@JsonProperty
does not use the class's configured naming strategy.Related Issue
Motivation and Context
How Has This Been Tested?
Documentation:
Checklist: