-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Flask 2.2.0 json_encoder
and json_decoder
are deprecated
#492
Comments
Thank you for the heads up, looks like there are a few things I need to update for this newest flask release. I will try to get everything updated in the next day or two here! |
Looking into this and it seems not as easy to switch to the new concept used by flask regarding json:
PS: It seems like the case @Sir-MaNiAl mentions where encoding fails is not covered by any tests. |
In a first step (Commig 4f18aca) I just reused to old Flask JSONEncoder class and use this as default. However, this will break of someone uses a custom JSON Encoder. |
Fix released in version |
Since Flask 2.2.0 json_encoder and json_decoder properties on
app
are deprecated and was set toNone
by default (Flask changelog)JWTManager._encode_jwt_from_config
method relies on it. It now raises errors on datetime, UUID, etc. values serialisation.The text was updated successfully, but these errors were encountered: