You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Difference i can see from connexion 2.0 to 3.0 flask is no longer a fully fledged subsistem but a subset of elements.
This means flask/werkzeug is not functional by themself after you start "FlaskApplication".
EG:
We are not able to use test_client from flask, we instead need to use connexion test_client -> problem with this is they don't share same API and would be too much while keeping compat with starlete subsystem?
Also flask/werkzeug by itself will be missing current_app context which breaks many features and libs for flask "flask limiter" as eg
To my opinion:
Connexion is a beloved lib but it lacks resources like Flask/werkzeug does, so would be for connexion too burdensome to not fully take advance and be fully compatible with flask, we can have small quirks but we should support the main flask features.
Flask/werkzeug should be a fully fledged subsystem or just a subset to help connexion
Fully operational subsystem
100%
Just subset, we should implement our own middlewares for everything
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Difference i can see from connexion 2.0 to 3.0 flask is no longer a fully fledged subsistem but a subset of elements.
This means flask/werkzeug is not functional by themself after you start "FlaskApplication".
EG:
To my opinion:
Connexion is a beloved lib but it lacks resources like Flask/werkzeug does, so would be for connexion too burdensome to not fully take advance and be fully compatible with flask, we can have small quirks but we should support the main flask features.
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions