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
As briefly discussed, here's a separate issue to track the feature request to allow the "production" of aliases, i.e. configure aliases globally similar to a PropertyNamingStrategy. Being able to do so would be great for backwards compatibility with existing JSON files when migrating from one naming style to the other.
Example: When changing serialization to use snake-style instead of camel-case, it would be great if deserialization would still accept camel-case to be able to read already written out files. Newly written files would only use snake-style, though.
The text was updated successfully, but these errors were encountered:
As briefly discussed, here's a separate issue to track the feature request to allow the "production" of aliases, i.e. configure aliases globally similar to a
PropertyNamingStrategy
. Being able to do so would be great for backwards compatibility with existing JSON files when migrating from one naming style to the other.Example: When changing serialization to use snake-style instead of camel-case, it would be great if deserialization would still accept camel-case to be able to read already written out files. Newly written files would only use snake-style, though.
The text was updated successfully, but these errors were encountered: