-
Notifications
You must be signed in to change notification settings - Fork 421
Feature request: Event Source Data Classes for API Gateway WebSocket events #6161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Bem-vindo de volta @ericbn! Super nice see you here again! Yes, it makes perfect sense to add these models to the event source as well. Do you want to submit a PR for this? These other requests are more related to creating a Resolver for WebSocket APIs, but I'd like to explore more ideas before deciding on that. |
Oi @leandrodamascena. Thanks! I can help with a PR. It's just not something I already started working at. |
No rush at all! Take your time and if you need any help with this PR, please let me know. |
Oi @leandrodamascena. Just created a PR: #6287 |
|
Use case
I see Pydantic models were added for API Gateway WebSocket events here:
This is request to add the corresponding Event Source Data Classes.
Solution/User Experience
It would be used like below, as an example:
Alternative solutions
I see other requests related to API Gateway WebSocket events, but they seem like different features: #1165, #5905
Acknowledgment
The text was updated successfully, but these errors were encountered: