-
Notifications
You must be signed in to change notification settings - Fork 421
Bug: custom serializer isn't being used by nested dict #4658
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. |
Hey @LironEr thanks for opening this issue! I see your point here and I agree that we should pass |
Since this is a bug, I've created a draft PR with the fix. At a first glance, we seem to be missing in other data types too so I'll look into those later before getting a review. PS: To prevent getting lost in translation, by "do you want to work in a PR to fix this?" was meant as a "if can help out we can prioritize this for the next release".. just in case : D |
|
Oops missed the notifications about that |
This is now released under 2.41.0 version! |
Expected Behaviour
The custom serializer should be passed to all sub-functions
Current Behaviour
The custom serializer is not being called, it's passed only on the first
jsonable_encoder
run.https://github.com/aws-powertools/powertools-lambda-python/blob/develop/aws_lambda_powertools/event_handler/openapi/encoders.py#L112
Code snippet
Possible Solution
pass
custom_serializer
to all functions, as this is a recursive function as mentioned in #3892 (comment)Steps to Reproduce
run the code snippet (:
Powertools for AWS Lambda (Python) version
2.40.1
AWS Lambda function runtime
3.11
Packaging format used
PyPi
Debugging logs
The text was updated successfully, but these errors were encountered: