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
Under your Advanced Usage in the README docs it mentions how to expose the request context in a websocket handler using:
with app.request_context(ws.environ):
Is there a recommended way to do this so that the request context is available to other decorators? Say I have a @login_required decorator that invokes a check for a cookie or header? Should I roll my own decorator that combines the two? Do I need to unroll the @login_required decorator to occur as inline code after I've exposed the request context?
Under your
Advanced Usage
in the README docs it mentions how to expose the request context in a websocket handler using:Is there a recommended way to do this so that the request context is available to other decorators? Say I have a
@login_required
decorator that invokes a check for a cookie or header? Should I roll my own decorator that combines the two? Do I need to unroll the@login_required
decorator to occur as inline code after I've exposed the request context?Where
@login_required
expects to find the request context.The text was updated successfully, but these errors were encountered: