-
Notifications
You must be signed in to change notification settings - Fork 402
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(jmespath_util): snippets split, improved, and lint #1419
docs(jmespath_util): snippets split, improved, and lint #1419
Conversation
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
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.
That's a great start, thank you so much @leandrodamascena !
Because we're refactoring, more than splitting doc snippets, we should strive for consistency and improved examples - like actual handler functions, maybe custom functions, try/except depending on the use case demonstrated, etc.
examples/jmespath_functions/src/powertools_base64_gzip_jmespath_function.py
Outdated
Show resolved
Hide resolved
examples/jmespath_functions/src/powertools_base64_jmespath_function.py
Outdated
Show resolved
Hide resolved
examples/jmespath_functions/src/powertools_custom_jmespath_function.py
Outdated
Show resolved
Hide resolved
examples/jmespath_functions/src/powertools_json_idempotency_jmespath.py
Outdated
Show resolved
Hide resolved
examples/jmespath_functions/src/powertools_json_jmespath_function.py
Outdated
Show resolved
Hide resolved
Hi Heitor! I understood the point and I will improve examples, typing, exception handling and others. I will work on this PR in the next few days and then I can send the others. |
… - generic envelope
… - generic envelope (small fixes)
… - generic envelope (small fixes)
… - generic envelope (small fixes)
… - generic envelope (highlight code)
… - generic envelope - changing to more clean and userful code
… - generic envelope - changing to more clean and userful code
Thank you so much Leandro! I've pushed a few changes to address cosmetic issues and use unused function arguments in some places, like introducing httpbin.org to simulate a dummy payment subscription. Merging! |
* develop: chore(ci): update changelog with latest changes docs(parser): minor grammar fix (aws-powertools#1427) chore(ci): update changelog with latest changes docs(apigateway): removes duplicate admonition (aws-powertools#1426) chore(ci): update changelog with latest changes docs(jmespath_util): snippets split, improved, and lint (aws-powertools#1419) chore(ci): reduce payload and only send prod notification
Issue number: #1374
Summary
Changes
Changes snippet fictitious names to real code snippet filenames for easier discovery and collaboration to improve/correct document snippets.
Some examples have also been refactored so that the codes are complete and there are no lint/pre-commit hooks issues.
User experience
Before
After
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.
View rendered docs/utilities/jmespath_functions.md