-
Notifications
You must be signed in to change notification settings - Fork 161
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.)validationThis item relates to the Validation UtilityThis item relates to the Validation Utility
Description
Summary
To kick off the development of the new Validation utility we need to add a new npm workspace for it.
Why is this needed?
To reduce the barrier of entry and friction to contributing to this new utility.
Which area does this relate to?
Validation
Solution
Initialize a placeholder npm workspace under packages/validation
.
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.)validationThis item relates to the Validation UtilityThis item relates to the Validation Utility
Type
Projects
Status
Shipped