Feature request: JMESPath abstract syntax tree (AST) #2210
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 the components of its abstract syntax tree (aka AST).
In the context of a JMESPath parser, an Abstract Syntax Tree (AST) is a hierarchical representation of the syntactic structure of a JMESPath expression. It abstracts away from the specifics of the input text and instead captures the components and relationships between them.
The creation of an AST typically follows the parsing stage, where the lexer has tokenized the input expression (#2205) and the parser has analyzed the sequence of tokens to identify the syntactic structure according to the JMESPath grammar rules (#2192).
Once constructed, the AST will be used by the tree interpreter (#2209) that will traverse it and evaluate the expression against the actual payload.
Solution/User Experience
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: