issue 19 JSON Deserialization Should Allow Missing - allow missing fi… #39
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
…elds by considering 'undefined' and 'null' to be the same in the Node.isNull() method
|
This is not the way so solve the problem. What if |
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.
Per #19, allow missing fields during JSON deserialization by considering 'undefined' and 'null' to be the same in the Node.isNull() method.
This is a desirable feature for a project I'm involved with. We have a large java type that is being passed in REST responses with values that are often null. The type is large enough that the byte savings from excluding null fields is the response is worth it. This feature would allow that.