Enabling testing for a pointer that references a nonexistent value ex… #41
Conversation
This file contains 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
…plicitly being null
dr3s
reviewed
Jan 19, 2017
| } | ||
| ] | ||
| } |
There was a problem hiding this comment.
this newline is very important for windows 98 json parsers
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.
We are trying to write a JSON Patch test operation that asserts the value at a path is not set.
Per the "Error Handling" section of the RFC on JSON Pointers:
A JSON Patch test operation can only test that evaluating a JSON pointer results in a specified value. I would like to consider that processing a JSON Pointer for the application of a JSON Patch test operation would evaluate a nonexistent value as null, at least when comparing to null.