-
Notifications
You must be signed in to change notification settings - Fork 153
chore: rename project to Powertools for AWS Lambda (TypeScript) #1472
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
Conversation
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.
Thank you for the PR.
I have suggested & committed a couple of changes, mostly in comments near the code where the name was redundant in the first place. In a couple of other instances where the full name was used multiple times in the same sentence/paragraph I have abbreviated the second occurrence to Powertools for AWS
as agreed.
The only place that I am not sure we should change are the tiles in the docs/we_made_this.md file/page.
These are blog posts written by the community so I think we should leave the titles as they are in the original unless they are updated at some point in the future. We can still however keep the changes in our description of them, i.e.
Power-up Lambda functions with AWS Lambda Powertools for TypeScript
should stay as it is since it's a title, but the sentence below that reads is post shows how to use Powertools for AWS Lambda (TypeScript) to quickly build Well-Architected serverless applications.
can be updated since it's written by us.
What do you think?
I agree with the docs/we_made_this.md file, I'll revert it. |
Description of your changes
Found and replaced references of the old name to the new one: Powertools for AWS Lambda (TypeScript)
Related issues, RFCs
Issue number: #1471
Checklist
Breaking change checklist
Is it a breaking change?: NO
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.