Skip to content

Maintenance: change project name to "AWS Lambda Powertools for TypeScript" #624

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.

Sign up for GitHub

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

Jump to bottom
Closed
saragerion opened this issue Mar 3, 2022 · 1 comment · Fixed by #628
Closed

Maintenance: change project name to "AWS Lambda Powertools for TypeScript" #624

saragerion opened this issue Mar 3, 2022 · 1 comment · Fixed by #628
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
production-ready-...

Comments

@saragerion
Copy link
Contributor

saragerion commented Mar 3, 2022 •
edited
Loading

Description of the improvement

Summary of the proposal

Change project name being referenced from these versions:

  • AWS Lambda Powertools (TypeScript)
  • Lambda Powertools TypeScript
  • AWS Lambda Powertools TypeScript

To this:
AWS Lambda Powertools for TypeScript

See related RFC for more information

How, where did you look for information

  • Readme files (root folder, nested project folders)
  • Mkdocs files in docs
  • Code
  • ...

We probably need to do a text search in the whole repo.

Missing or unclear documentation

Inconsistent naming convention, see related RFC.

Improvement

A consistent name throught the project.

Related existing documentation

N/A

Related issues, RFCs

aws-powertools/powertools-lambda#80
@saragerion saragerion added documentation Improvements or additions to documentation good-first-issue Something that is suitable for those who want to start contributing priority:low labels Mar 3, 2022
@saragerion saragerion added this to the production-ready-release milestone Mar 3, 2022
@saragerion saragerion changed the title Documentation (all): change project name to "AWS Lambda Powertools for TypeScript" Documentation: change project name to "AWS Lambda Powertools for TypeScript" Mar 3, 2022
@goverdhan07 goverdhan07 mentioned this issue Mar 4, 2022
Merged
4 tasks
@dreamorosi dreamorosi linked a pull request Mar 8, 2022 that will close this issue
docs: updated project names to aws lambda power tools for typescript #628
Merged
4 tasks
@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2022

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

@dreamorosi dreamorosi changed the title Documentation: change project name to "AWS Lambda Powertools for TypeScript" Maintenance: change project name to "AWS Lambda Powertools for TypeScript" Nov 14, 2022
@dreamorosi dreamorosi added internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) completed This item is complete and has been merged/shipped and removed good-first-issue Something that is suitable for those who want to start contributing labels Nov 14, 2022
@dreamorosi dreamorosi self-assigned this Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
None yet
Milestone
production-ready-release
2 participants
@dreamorosi @saragerion