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

Allow "production" of aliases to assist with naming style migration #2072

Open
sschuberth opened this issue Jun 22, 2018 · 1 comment
Open

Comments

@sschuberth
Copy link
Contributor

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.

@tyrantkhan
Copy link

would love this feature!

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

No branches or pull requests

2 participants