You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think framework should be flexible to allow developer to choose which naming strategy they would prefer to use, on spring boot application when we import DxaSpringInitialization class it force us to use UpperCamelCase strategy.
I saw there is reason to do UpperCamelCase strategy on object mapper
objectMapper.setPropertyNamingStrategy(new UpperCamelCaseStrategy());
but that strategy then applies globally.
instead of add strategy on bean initialization, i feel it would be better if we make @JsonNaming(PropertyNamingStrategy.UpperCamelCaseStrategy.class) annotation on specific class i.e. MvcModelData.
that would make framework more flexible and other application which is using dxa can choose jackson naming strategy.
The text was updated successfully, but these errors were encountered:
Hi,
I think framework should be flexible to allow developer to choose which naming strategy they would prefer to use, on spring boot application when we import DxaSpringInitialization class it force us to use UpperCamelCase strategy.
I saw there is reason to do UpperCamelCase strategy on object mapper
objectMapper.setPropertyNamingStrategy(new UpperCamelCaseStrategy());
but that strategy then applies globally.
instead of add strategy on bean initialization, i feel it would be better if we make @JsonNaming(PropertyNamingStrategy.UpperCamelCaseStrategy.class) annotation on specific class i.e. MvcModelData.
that would make framework more flexible and other application which is using dxa can choose jackson naming strategy.
The text was updated successfully, but these errors were encountered: