-
Notifications
You must be signed in to change notification settings - Fork 405
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
docs(idempotency): fix description in Advanced
table
#5191
docs(idempotency): fix description in Advanced
table
#5191
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
Hi @garysassano! Thank you very much for submitting this PR! We made some changes to our branches because we had to release V3 and this PR became impossible to merge due to too many conflicts. Do you mind closing this PR and opening another one against develop? You may need to pull the repository/branches again because we changed a lot. |
@leandrodamascena I updated my branch. |
Thanks a lot @garysassano! I'm approving this PR and will wait for @dreamorosi to merge it into TS before merging it here. Since you're working there, I'll wait to see if there are any other changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APPROVED!
Quality Gate passedIssues Measures |
I just merged the the corresponding PR on the TS repo, feel free to merge this whenever you want. |
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
Issue number: #5193
Summary
Changes
payload_validation_jmespath
to make it more clearIssue: #5193
Related TS Issue: aws-powertools/powertools-lambda-typescript#3098
Related TS PR: aws-powertools/powertools-lambda-typescript#3092
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.