Closed greyli closed 1 year ago
Great question.
FWIW, if it's painful to retain backwards compatibility, don't be afraid to also drop support for Flask < 3.x. Most of those users will be fine with the older releases of Flask-DebugToolbar
, and the ones who are currently broken are on newer Flask. Plus given the limited maintenance time this project receives, better to fix forward and start from a cleanish slate if needed. Whatever seems better to you two.
This change won't break the Flask 2.x and Flask 1.x compatibility.
Merged. I updated the test database URL to the in-memory SQLite database so that it will work on Windows.
This decorator has been removed in Flask 3.0.