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
The Advanced Usage section in the README says that ws.environ should be used where ws = <flavor>WebSocket(app). However, WebSocket and descendants don't have an environ member.
It looks like a reference to the environ is only retained in the WebSocketClient instance which is not readily accessible from the WebSocket, so perhaps this wasn't implemented. #77 is a strong hint supporting that.
Can anyone recommend a way to access to the request context in a websocket route?
The text was updated successfully, but these errors were encountered:
The
Advanced Usage
section in the README says thatws.environ
should be used wherews = <flavor>WebSocket(app)
. However, WebSocket and descendants don't have an environ member.It looks like a reference to the environ is only retained in the
WebSocketClient
instance which is not readily accessible from theWebSocket
, so perhaps this wasn't implemented. #77 is a strong hint supporting that.Can anyone recommend a way to access to the request context in a websocket route?
The text was updated successfully, but these errors were encountered: