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

Multiple aliases #101

Open
andreaslarssen opened this issue Jun 25, 2019 · 2 comments
Open

Multiple aliases #101

andreaslarssen opened this issue Jun 25, 2019 · 2 comments

Comments

@andreaslarssen
Copy link

It would be nice to have an alias for deserialization, and one for serialization.
Is there a way to achieve this other than writing custom de-/serializer?

@andreaslarssen
Copy link
Author

...and multiple serialize AND deserialize aliases?

@1R053
Copy link
Collaborator

1R053 commented Jun 25, 2019

for deserialization it is possible to use the "beforeDeserialization" handler to inspect and modify the the JSON object as required on any level of a nested object. This should give much more flexibility than an alias based solution, especially across multiple schema migrations.

for serializations I do not yet see, why this is a relevant use case.

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

No branches or pull requests

2 participants