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
Some third-party WebSocket clients, like ws, may integrate a manual HTTP handshake for WebSocket connections. If such occur, Interceptors should handle them appropriately.
I am raising this in MSW because Interceptors may be too low-level of a library to handle this. Effectively, where we do this doesn't matter. Just has to be accounted for.
Proposal
The handshake handling itself isn't that complicated:
What's complicated is the ergonomics of a handler (ws link) that unfolds into multiple handlers (ws + http.get). MSW doesn't have a concept of a compound handler like that at the moment, and I would hate to ask people to spread ...ws.link() in their handlers.
The text was updated successfully, but these errors were encountered:
Scope
Improves an existing behavior
Compatibility
Feature description
Summary
Some third-party WebSocket clients, like
ws
, may integrate a manual HTTP handshake for WebSocket connections. If such occur, Interceptors should handle them appropriately.I am raising this in MSW because Interceptors may be too low-level of a library to handle this. Effectively, where we do this doesn't matter. Just has to be accounted for.
Proposal
The handshake handling itself isn't that complicated:
What's complicated is the ergonomics of a handler (ws link) that unfolds into multiple handlers (ws + http.get). MSW doesn't have a concept of a compound handler like that at the moment, and I would hate to ask people to spread
...ws.link()
in their handlers.The text was updated successfully, but these errors were encountered: