-
Notifications
You must be signed in to change notification settings - Fork 162
Closed
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Description
Summary
A few weeks ago we changed our tsconfig.json
file to adopt TypeScript 5.0 (#1672) and in doing so we inadvertently enabled the removeComments
option from the compilerOptions
. This caused the docstrings to be stripped from the built output.
We should set the option back to false
so that comments are kept.
Why is this needed?
So that customers can get info and examples about methods in their IDEs when using Powertools.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Type
Projects
Status
Shipped