feat(parser): add schema support for API Gateway WebSocket events #3807
+180
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
This PR introduces a new schema named
APIGatewayProxyWebsocketEventSchema
underpackages/parser/src/schemas/api-gateway-websocket.ts
. It enables developers to validate and parse WebSocket Lambda events using@aws-lambda-powertools/parser
.Additionally:
packages/parser/tests/events/apigw-websocket/connectEvent.json
packages/parser/tests/unit/schema/apigw-websocket.test.ts
using thegetTestEvent
utilityheaders
,multiValueHeaders
,queryStringParameters
,stageVariables
,requestContext
, andbody
This schema follows the same structure as other API Gateway events and enables first-class support for
$connect
,$disconnect
, and$message
WebSocket routes in Lambda.Issue number: closes #3787
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.