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
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: