fix(websocket): keep messages socket alive across route changes#316
Merged
Conversation
Stop disconnecting /ws/messages/ when pathname or toast identity changes; use a pathname ref for toast suppression and register auth listeners once. Fixes #315
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #315 — the global
/ws/messages/WebSocket was torn down on every client-side navigation becauseWebSocketProviderlistedlocation.pathnameandtoastin the connectionuseEffectdependencies.config.apis.meshBot.baseUrltoastinstead ofuseToast()in the connection effectwebsocketService.initialize()only onceTesting performed
WebSocketProvider.test.tsx(navigation does not calldisconnect; toast suppression on/messages)npm test— 352 tests passed