Thanks for looking into this!

Another option that might be worth considering is to follow suite with flask and depreciate the json encoder options as part of this extension, and mark that release as requiring flask >= 2.3. But that's just a thought I had when I woke up and without any caffeine so I want to think on it some more 😄

Edit: Should have had my coffee. I didn't look at this closely enough to realize why we have this option, it's to bridge the gap between flask and pyjwt.

Actually many other extensions will also run into problems: Flask-SQLALchemy (pallets-eco/flask-sqlalchemy#1068), Flask-Security / Flask-Security-Too (pallets/flask#4711) just to name the few I use most. Flask 2.3 will require quite a bit of changes in extensions as so many things will be removed / restructured / change. Maybe it's worth to keep an eye on other extensions and see how they handle the issues.

I'm right now working on this to fix the reviewd changes. Don't expect the optimal solution but I try to at least reach these goals:

• Be compatible with Flask < 2.2 where flask.json.JSONEncoder exists
• Be forward compatible with Flask >= 2.2 where the JSONEncoder generates deprecation warnings and be prepared once the decoder is removed.

I think this would be a good starting point to going further.

I'm right now working on this to fix the reviewd changes. Don't expect the optimal solution but I try to at least reach these goals:

* Be compatible with Flask < 2.2 where flask.json.JSONEncoder exists

* Be forward compatible with Flask >= 2.2 where the JSONEncoder generates deprecation warnings and be prepared once the decoder is removed.

I think this would be a good starting point to going further.

Sounds great to me! I'll be around to help this get merged and a new release cut, and then digging into a more optimal solution can happen after. Thanks for your work on this!! 🥳 👍

I pushed some new code:

• Works with flask <2.2 and flask >= 2.2
• Does currently not respect the flask.json_provider_class setting and uses conditional imports to get a valid encoder (see json_encoder.py)
• Coverage Test might fail as coverage is only run with one flask version and misses the conditional import code for the other flask version.

Damn, now you where faster than me... I was working on a simmilar idea, with the additional benefit that the new app.json_provider_class was respected in case of Flask >= 2.2....

Damn, now you where faster than me... I was working on a simmilar idea, with the additional benefit that the new app.json_provider_class was respected in case of Flask >= 2.2....

Sorry, didn't mean to step on your toes here, just had some time so figured I would take a stab at it! If you have a different idea please feel free to revert that last commit and push your stuff up!

No problem at all! Nice to see other motivated devs working on this! Things in my latest commit:

• respect app.json_provider_class. However this requires some hacky way to generate a JSONEncoder class on the fly...
• moved from json_encoder.py to internal_utils.py
• Documented the stuff I did.

If this sound reasonable I will push the changes. I have also updated tox.ini to test with flask < 2.2 and flask > 2.2, I can also push this if you want.

No problem at all! Nice to see other motivated devs working on this! Things in my latest commit:

* respect `app.json_provider_class`. However this requires some hacky way to generate a JSONEncoder class on the fly...

* moved from `json_encoder.py` to `internal_utils.py`

* Documented the stuff I did.

If this sound reasonable I will push the changes. I have also updated tox.ini to test with flask < 2.2 and flask > 2.2, I can also push this if you want.

That would be awesome! Thank you for the very thorough work you're doing on this!! 👍

Ok, I force-pushed my changes. Let's see what you think.

Looks good. Left one small thought that I think is probably worth changing just to be safe, but overall I like the approach. Thanks!

Amazing ! Could you release this soon ? :)

It's up as version 4.4.4. Cheers!