-
Notifications
You must be signed in to change notification settings - Fork 161
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 UtilitytestsPRs that add or change testsPRs that add or change tests
Description
Summary
To continue the migration from Jest to Vitest we need to move over the tests for the jmespath
package to use the new test runner.
Why is this needed?
So that we can continue our efforts of removing dev dependencies and streamline the tests.
Which area does this relate to?
JMESPath
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 UtilitytestsPRs that add or change testsPRs that add or change tests
Type
Projects
Status
Shipped