use custom JSON encoding if specified #1477
Merged
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.
If a class extended JsonSupport and provided a custom encoding it would get used by the interited methods, but would get ignored when using
Json.encode
. This could create problems when an object is nested because the custom encode would not get used. TheJson.encode
could not directly call encode, because it would create a loop with the default implementation.This change adds a method that can indicate if it is desirable for
Json.ecnode
to use the custom encoding.