Skip to content
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.

Sign up for GitHub

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

Jump to bottom

InvalidPathException in RelationalOperator depending on Locale #600

Closed
renekrie opened this issue Feb 29, 2020 · 0 comments · Fixed by #601
Closed

InvalidPathException in RelationalOperator depending on Locale #600

renekrie opened this issue Feb 29, 2020 · 0 comments · Fixed by #601

Comments

@renekrie
Copy link
Contributor

RelationalOperator.fromString(operatorString) will throw an InvalidPathException if the default Locale is tr_TR and operatorString is "in".

This happens because the implementation applies an .toUpperCase on the operatorString without passing a Locale. At least in Turkish, and maybe in other orthographies as well, the uppercase variant does not match what was defined as the uppercase operatorString in RelationalOperator.

I'm going to supply a fix for this.
renekrie added a commit to renekrie/JsonPath that referenced this issue Feb 29, 2020
@renekrie
Avoid Locale-dependant InvalidPathException in RelationalOperator, fixes
698dbfa 
 json-path#600
@renekrie renekrie mentioned this issue Feb 29, 2020
Merged
kallestenflo added a commit that referenced this issue Dec 10, 2020
@kallestenflo
Merge pull request #601 from renekrie/issue600
ba35cf9 
Avoid InvalidPathException in RelationalOperator, fixes #600
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Avoid InvalidPathException in RelationalOperator, fixes #600 renekrie/JsonPath
1 participant
@renekrie