-
Notifications
You must be signed in to change notification settings - Fork 429
Bug: v2.40.0 undocumented breaking change in Router #4650
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
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Checking now. |
Hi @karvetskiy, thanks for opening this issue and reporting this bug. Our tests didn't catch accessing Thanks |
Hey @karvetskiy! If I publish a pre-release on Pypi, can you test if the issue is resolved in your environment before we release a new patch release? Thanks |
Hey @leandrodamascena! Just checked alpha version, still can't access |
he hasn't published yet, will ping you shortly @karvetskiy |
PR incoming, we've been wrestling with static typing and additional tests to be quadruple sure this would work on areas we were missing tests too. Once we merge and publish the alpha release we ping you |
kicked off pre-release (should be in PyPi in ~6 minutes or so).. https://github.com/aws-powertools/powertools-lambda-python/actions/runs/9712027684 |
Hey @karvetskiy! alpha release is available. Can you test pls? |
This is now released under 2.40.1 version! |
Expected Behaviour
In out code we accessed
current_event
directly fromRouter
class befor 2.40.0Current Behaviour
In 2.40.0 version
current_event
available inAppSyncResolver
onlyCode snippet
Possible Solution
No response
Steps to Reproduce
call
current_event
attribute from Router classPowertools for AWS Lambda (Python) version
2.40.0
AWS Lambda function runtime
3.12
Packaging format used
Lambda Layers
Debugging logs
No response
The text was updated successfully, but these errors were encountered: