-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[JsonPath] Fix throwing on quoted True/False/Null #62465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
It looks like you unchecked the "Allow edits from maintainer" box. That is fine, but please note that if you have multiple commits, you'll need to squash your commits into one before this can be merged. Or, you can check the "Allow edits from maintainers" box and the maintainer can squash for you. Cheers! Carsonbot |
|
I see that you added tests in |
|
I would suggest submitting those new tests upstream in https://github.com/jsonpath-standard/jsonpath-compliance-test-suite/ as they might be valuable to other implementations of the standard. |
540c64c to
340cb47
Compare
|
Hah I just moved it to unit tests, will go back then |
7fb3711 to
6b0e1c2
Compare
|
@alexandre-daubois @stof Done, btw there are 2 (unrelated) test cases upstream which now fail here when we update the json: |
|
Thanks for taking care of the upstream change! I'll have a look at the failing test with the updated set. |
|
It has been merged upstream. Can you update the |
6b0e1c2 to
d761e25
Compare
Done |
alexandre-daubois
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for tackling this!
|
Thank you @TamasSzigeti. |
Bumped into this when parsing Kubernetes json output where
"True"is commonly used and JsonPath threw for this valid expression. Making the regex more strict fixes it.See also PR for upstream fixtures