Open
Conversation
This adds support for (De)Serializer handlers which can be used to modify how a class is (de-)serialized. An example here is the `uuid` package from symfony or ramsey where the class should be serialized to a string and not an object.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds support for (De)Serializer handlers which can be used to modify how a class is (de-)serialized. A good example is the
uuidpackage from symfony or ramsey where the class should be serialized to a string and not an object.This is (somehwat) a proof of concept to get a discussion starting, because I'm not sure if this is the right approach, but there are some use cases where it just does not make sense to add native support in this library, but rather give the user of the library the possibility to add different (de-)serialization.