Handling nulls in instances #573
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
Julian
reviewed
Jul 6, 2022
|
LGTM at this point, merge at will. |
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.
These tests address a scenario described in Slack.
Essentially, .Net doesn't separate the ideas of JSON null (pertaining to data) and object-reference null (pertaining to programming). Instead they represent JSON null as object-reference null, and it's caused some problems in my implementation.
These test cases would have caught these issues.
As I suspect it's possible that other languages such as C/C++ or Java may also have similar JSON data model issues, I figured adding these scenarios to the test suite could help.