[JsonPath] Better handling of unicode chars in expressions #60681
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
54e35eb to
f12c05c
Compare
stof
approved these changes
Jun 4, 2025
f0b5dfc to
251f3b9
Compare
251f3b9 to
4a4c760
Compare
4a4c760 to
ab26bc2
Compare
stof
requested changes
Jun 4, 2025
0e8cc33 to
cefc5d9
Compare
cefc5d9 to
75029db
Compare
75029db to
d56b148
Compare
|
Ah yes, I relied a bit too much on fabbot and missed checks on CS. Sorry for the manual lint! |
|
Thank you @alexandre-daubois. |
Merged
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.
Handle all types of Unicode characters in expressions: control chars, surrogate, etc.