-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
batchThis item relates to the Batch Processing UtilityThis item relates to the Batch Processing UtilitycompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippeddocumentationImprovements or additions to documentationImprovements or additions to documentationinternalPRs 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
This issue is part of a larger group: #2381
As part of this task we should:
- review that the README file for the package is relevant for customers and follow the structure described in the parent issue
- review the API docs and apply the conventions described in the parent issue
Why is this needed?
So that customers finding the package on npm or using the API docs have the right level of details.
Which area does this relate to?
Other
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
batchThis item relates to the Batch Processing UtilityThis item relates to the Batch Processing UtilitycompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippeddocumentationImprovements or additions to documentationImprovements or additions to documentationinternalPRs 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