-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document escaping rules for JsonPath patterns. #71
Comments
@DSinge what do you think? |
@curioustechizen can you point me to the other library that describes escaping them? I feel like this information has less to do with a specific library, and more to do with how JSONPath itself works, so I'd be hesitant to add that info to our documentation. I'm open to seeing what you can come up with though. |
Sorry I did not mean that other libraries mention it in their documentation. I meant that there seems to not be agreement among libraries on how to escape dots. For example the answers to this SO question seem to indicate that there are 2 distinct syntaxes for escaping dots.
|
I think the majority of implementations use the first approach, but I'll do some research and see if we should be calling this out. |
I had a key in my JSON that included dots. I found from some other JsonPath libraries that escaping them requires you to include a bracket and single quotes.
The docs already mention "Bracket-notated key value accessor for JSON objects" but it was not obvious to me that this should be used for escaping purposes. I'm not aware if there are other escaping rules to be aware of.
It would be nice to add this to the docs. I am willing to open a PR if you think that this is a valid point to add to the docs.
The text was updated successfully, but these errors were encountered: