Closed
Description
Use case
As part of the definition of a JMESPath utility we need to define the grammar supported by the module as well as the TypeScript types and errors that can be thrown by the utility.
The grammar should align with the JMESPath specification.
Solution/User Experience
All the types and errors should be documented and exposed to customers via API documentation. The grammar is treated as internal since it corresponds to the JMESPath specification.
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.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Shipped