Add option for explicitToJson
#228
Merged
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
|
Since |
|
See discussion in previous PR - #195 |
jakemac53
approved these changes
Jun 8, 2018
Allows users to opt-in to including `.toJson()` calls on nested objects in generated `toJson` methods. This is useful if you want to round-trip the output of toJson without putting it through jsonEncode and jsonDecode Fixes #192
kevmoo
force-pushed
the
i192_call_to_json_automatically
branch
from
253aa8a to
fd874dd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allows users to opt-in to including
.toJson()calls on nestedobjects in generated
toJsonmethods.This is useful if you want to round-trip the output of toJson without
putting it through jsonEncode and jsonDecode
Fixes #192