-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationparserThis item relates to the Parser UtilityThis item relates to the Parser Utility
Description
Summary
Most of the envelopes have return type ParsedResult<unknown, z.infer<T>>
which allow to infer the type from the schema used with the envelope. The envelopes EventBridge
, LambdaFunctionUrl
, VpcLattice
and VpcLatticeV2
have only ParsedResult
which we need to make more specific.
Why is this needed?
So it is easier to work with the types derived from the schema instead of casting it manually.
Which area does this relate to?
Parser
Solution
Add ParsedResult<unknown, z.infer<T>>
as a return type for safeParse
on the the envelopes mentioned above.
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
confirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationparserThis item relates to the Parser UtilityThis item relates to the Parser Utility
Type
Projects
Status
Shipped