generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 180
Closed as duplicate of#4516
Closed as duplicate of#4516
Copy link
Labels
rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future
Description
Use case
Per the docs, it would be great to have standard schema validation.
I'm sure this has been discussed in some detail internally, however I would find value in input and output validation. Additionally, we have also validated against route and query params occasionally.
I stubbed out a quick middleware and pulled in some of the parser middy middleware logic. My initial thought is typing is going to be difficult. Ideally, it would be great to have the validated request body schema typing available within the route.
Solution/User Experience
No proposed solution at this time; just opening this to initiate the discussion
Alternative solutions
Acknowledgment
- This feature 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
rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future
Type
Projects
Status
Closed