docs(parser): fix a a typo in SqsEnvelope#7052
docs(parser): fix a a typo in SqsEnvelope#7052leandrodamascena merged 2 commits intoaws-powertools:developfrom DustinAlandzes:patch-1
Conversation
Signed-off-by: Dustin Alandzes <5882512+DustinAlandzes@users.noreply.github.com>
pull-request-size
bot
added
the
size/XS
leandrodamascena
changed the title
|
Hey @DustinAlandzes thanks a lot for opening this PR to fix this typo! Can I ask you please to open an issue here: https://github.com/aws-powertools/powertools-lambda-python/issues/new?template=documentation_improvements.yml? Don't need to provide too much information, simples words are enough. Thanks. |
github-actions
bot
added
the
documentation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7052 +/- ##
========================================
Coverage 96.26% 96.26%
========================================
Files 275 275
Lines 12917 12917
Branches 955 955
========================================
Hits 12435 12435
Misses 376 376
Partials 106 106 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Thanks for the quick reply! I made an issue for this here: #7053 Let me know if you need anything else |
|
leandrodamascena
left a comment
leandrodamascena
left a comment
There was a problem hiding this comment.
Hey @DustinAlandzes! Thanks a lot for working on this PR!
APPROVED!
leandrodamascena
merged commit e51b767
into
aws-powertools:develop
2 participants
Issue number: #7053
Summary
There is a small spelling mistake in the docstring for SqsEnvelope.
Changes
npt -> not in a comment
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.