Add ExecutionContextSerializer implementation based on Gson #4185
Conversation
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
This is work in progress. Gson seems to deserialize custom types to Map instead of the original type (seems like type info is not serialized). TODO: Need to figure out if this should be done in the implementation of the serializer or as a configuration of the gson instance
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 is a draft PR. Gson seems to deserialize custom types to
Mapinstances instead of the original type (it looks like type information is not serialized).TODO: Need to figure out if this should be done in the implementation of the serializer or as a configuration of the gson instance.
Issue #4151