You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://docs.jsonata.org/simple says in part: "Field references containing whitespace or reserved tokens can be enclosed in backticks". This is great and has already been the answer a few times in querying some odd JSON documents we have. The question has come up: "What exactly are the reserved tokens that must be handled in this manner?"
We have stumbled across a few things we would not have guessed needed escaping, such as keys that start with numbers like "1Address", but are looking for a definitive list of things that must be escaped in this manner and are unable to find anything in the docs. Can this point be clarified?
The text was updated successfully, but these errors were encountered:
This is a documentation request, not a bug...
https://docs.jsonata.org/simple says in part: "Field references containing whitespace or reserved tokens can be enclosed in backticks". This is great and has already been the answer a few times in querying some odd JSON documents we have. The question has come up: "What exactly are the reserved tokens that must be handled in this manner?"
We have stumbled across a few things we would not have guessed needed escaping, such as keys that start with numbers like "1Address", but are looking for a definitive list of things that must be escaped in this manner and are unable to find anything in the docs. Can this point be clarified?
The text was updated successfully, but these errors were encountered: