Fix JSON Pointer regression #119
Draft
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
|
I'm not going to merge this, for now, and call it a bug which is now fixed. Shout if this is affecting you and we'll find a way to support non-string keys in JSON Pointer data. |
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.
Before PR #116 we would resolve JSON pointers pointing to dictionaries with integer keys. Noting that JSON object keys are always strings, this PR tentatively restores that feature in case anyone is relying on it.
I've also added support for resolving pointers pointing to float keys, provisionally. And, if we're supporting integer and float keys, why not bool and
None? (dictionaries and lists aren't hashable, so they can't be keys in Python or JSON).