Skip to content

Maintenance: migrate test runner to vitest for jmespath package #3078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 2 tasks
dreamorosi opened this issue Sep 16, 2024 · 2 comments · Fixed by #3079
Closed
1 of 2 tasks

Maintenance: migrate test runner to vitest for jmespath package #3078

dreamorosi opened this issue Sep 16, 2024 · 2 comments · Fixed by #3079
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) jmespath This item relates to the JMESPath Utility tests PRs that add or change tests

Comments

@dreamorosi
Copy link
Contributor

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation tests PRs that add or change tests jmespath This item relates to the JMESPath Utility labels Sep 16, 2024
@dreamorosi dreamorosi self-assigned this Sep 16, 2024
@dreamorosi dreamorosi mentioned this issue Sep 16, 2024
Merged
@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Sep 17, 2024
@dreamorosi dreamorosi linked a pull request Sep 17, 2024 that will close this issue
test(jmespath): switch tests to vitest #3079
Merged
@dreamorosi dreamorosi moved this from Triage to Shipped in Powertools for AWS Lambda (TypeScript) Sep 17, 2024
@dreamorosi dreamorosi moved this from Shipped to Coming soon in Powertools for AWS Lambda (TypeScript) Sep 17, 2024
@dreamorosi dreamorosi removed the triage This item has not been triaged by a maintainer, please wait label Sep 17, 2024
@github-actions GitHub Actions
Copy link
Contributor

⚠️ 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.

@dreamorosi dreamorosi mentioned this issue Sep 30, 2024
Open
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 8, 2024

This is now released under v2.9.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Oct 8, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) jmespath This item relates to the JMESPath Utility tests PRs that add or change tests
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test(jmespath): switch tests to vitest aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi