-
Notifications
You must be signed in to change notification settings - Fork 408
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
Feature request: introduce ALBRouter, etc. to set the type of current_event in the REST API Router #1781
Comments
hey @kt-hr, did you run into any issue when accessing It should work, please let us know otherwise with a snippet we can reproduce - Test, Docs Example, API reference |
hi @heitorlessa , thank you for your confirmation. Sorry, let me correct the content. I mistakenly thought I could not access properties because the IDE was showing an error. The type of |
Ahhh that makes more sense now - thanks for clarifying and updating the title. Let's do it - it should be fairly trivial as you can simply subclass, override the type like we did for each explicit resolver class ( Feel free to create a PR and we can review in January after we're back from winter holidays. Thank you! |
Hi @kt-hr just so I can understand this problem better, why are you not using |
Hi, @rubenfonseca thank you for checking. In my use case, I want to access properties such as
|
Great, I now get the problem! Will work on this today :) |
@kt-hr I opened a PR to fix the UX above, please feel free to leave your comment before we merge! |
@rubenfonseca thank you very much. Very helpful. I have nothing to add to that. |
|
This is now released under 2.6.0 version! |
This is now released under 2.8.0 version! |
Use case
In #761,
APIGatewayRestResolver
,APIGatewayHttpResolver
,ALBResolver
, andLambdaFunctionUrlResolver
were created to access all properties fromcurrent_event
.I would like to access all properties from
current_event
in router as well.Solution/User Experience
Alternative solutions
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: