Feature request: JMESPath abstract syntax tree (AST)

[dreamorosi]

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

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

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.