Feature: Add ability to reconnect websockets #4526
Draft
+43
−18
Conversation
This file contains 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
|
@tofarr I'd rather not expose this to the user. 99% of the time we should be able to auto-reconnect (e.g. if a pod rolls or we do a new deployment, they can connect to a different pod seamlessly) If the socket is disconnected and stays disconnected though, having the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the websocket is disconnected in the frontend, the UI displays this users are given a button to reconnect.
For the moment, the button just does a page refresh, but I could see a future where it calls a context created in the App component.
