Feature request: JMESPath parser

[dreamorosi]

Use case

As part of the JMESPath utility implementation we need to define a parser.

The parser is the main orchestrator component and uses a lexer (#2205), AST (#2210), and tree interpreter (#2209) to tokenize, abstract, and traverse the JMESPath expression and produce a result.

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.