The request scope name directly clashes with the global request variable in Flask. Even when using the injector-style approach and injecting flask.Request into your handlers/services, the developer might still want to use a descriptive name like request for it, raising an issue again.
Since renaming the scope would not be backwards-compatible, it would be nice if Flask-Injector could at least provide a second alias like request_scoped to avoid stuff like
from flask_injector import request as request_scoped
.
The
requestscope name directly clashes with the globalrequestvariable in Flask. Even when using theinjector-style approach and injectingflask.Requestinto your handlers/services, the developer might still want to use a descriptive name likerequestfor it, raising an issue again.Since renaming the scope would not be backwards-compatible, it would be nice if
Flask-Injectorcould at least provide a second alias likerequest_scopedto avoid stuff likefrom flask_injector import request as request_scoped.