You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreamorosi opened this issue
Mar 25, 2024
· 2 comments
· Fixed by #2271
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)jmespathThis item relates to the JMESPath Utility
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.
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.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
confirmed
The scope is clear, ready for implementation
jmespath
This item relates to the JMESPath Utility
labels
Mar 25, 2024
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)jmespathThis item relates to the JMESPath Utility
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
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: