Skip to content
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.

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

Maintenance: reach 100% JMESPath test coverage & spec compliance #2270

Closed
1 of 2 tasks
dreamorosi opened this issue Mar 25, 2024 · 2 comments · Fixed by #2271
Closed
1 of 2 tasks

Maintenance: reach 100% JMESPath test coverage & spec compliance #2270

dreamorosi opened this issue Mar 25, 2024 · 2 comments · Fixed by #2271
Assignees
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

Comments

@dreamorosi
Copy link
Contributor

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.

@dreamorosi 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
@dreamorosi dreamorosi self-assigned this Mar 25, 2024
@dreamorosi dreamorosi moved this from Triage to Pending review in Powertools for AWS Lambda (TypeScript) Mar 25, 2024
@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 Mar 27, 2024
@dreamorosi dreamorosi linked a pull request Mar 27, 2024 that will close this issue
9 tasks
@dreamorosi dreamorosi moved this from Pending review to Coming soon in Powertools for AWS Lambda (TypeScript) Mar 27, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Mar 27, 2024
@github-project-automation github-project-automation bot moved this from Shipped to Coming soon in Powertools for AWS Lambda (TypeScript) Mar 27, 2024
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.

Copy link
Contributor

This is now released under v2.0.4 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 Apr 10, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Development

Successfully merging a pull request may close this issue.

1 participant