Properly constrain non-string json_pointer overloads#3681
Merged
Conversation
Owner
|
In which order should this be merged? After #3663? |
Contributor
Author
|
Shouldn't matter since this one doesn't touch |
shaischaudhry
approved these changes
Aug 6, 2022
Thanks, @alex-700, for reminding me.
9868e18 to
8cc150c
Compare
Contributor
Author
falbrechtskirchinger
left a comment
There was a problem hiding this comment.
Looks good to me.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Add missing
is_basic_jsonconstraints to the deprecated non-string json_pointer overloads.Thanks, @alex-700, for reminding me.
Compared to #3658, the
value()functions and the regression test have been omitted. Both are handled in #3663.Closes #3658.