generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 179
Closed
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)jmespathThis item relates to the JMESPath UtilityThis item relates to the JMESPath Utility
Description
Summary
As part of the JMESPath utility implementation we should add test coverage and compliance according to the official compliance test suite that can be found here.
Why is this needed?
So that we can have a modicum of confidence that the utility behaves according to the specification.
Which area does this relate to?
Tests
Solution
No response
Acknowledgment
- This 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
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)jmespathThis item relates to the JMESPath UtilityThis item relates to the JMESPath Utility
Type
Projects
Status
Shipped