Closed
Description
Use case
Customers on the AWS Community Builders Slack have reported that the null
type used for the identity
field in the types of the new AppSync Events solver are too strict.
This is correct, because the field can have different content based on the authorization method used.
Solution/User Experience
As per title, mark the field as unknown
in the types and explain in the docstring.
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
Type
Projects
Status
Shipped