-
Notifications
You must be signed in to change notification settings - Fork 149
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
Feature request: JMESPath tree interpreter #2209
Labels
completed
This item is complete and has been merged/shipped
feature-request
This item refers to a feature request for an existing or new utility
jmespath
This item relates to the JMESPath Utility
Comments
2 tasks
This was referenced Mar 12, 2024
9 tasks
9 tasks
9 tasks
This issue is now closed. Please be mindful that future comments are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. |
This is now released under v2.0.4 version! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
completed
This item is complete and has been merged/shipped
feature-request
This item refers to a feature request for an existing or new utility
jmespath
This item relates to the JMESPath Utility
Use case
As part of the JMESPath utility implementation we need to define a tree interpreter.
The tree interpreter serves as a component responsible for evaluating the Abstract Syntax Tree (AST) generated during the parsing process against a given JSON document. he purpose of the tree interpreter is to interpret the meaning of the JMESPath expression represented by the AST and to extract the relevant data from the JSON document accordingly.
The result of this evaluation will be the result of the query.
Solution/User Experience
The tree interpreter should use Vaughan R. Pratt's "Top Down Operator Precedence".
All types, classes, and functions should be documented and exposed to customers via API docs.
Alternative solutions
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: