-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not delete token on network error #178
Conversation
Codecov Report
@@ Coverage Diff @@
## master #178 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 40 40
Lines 1447 1447
=====================================
Hits 1447 1447 Continue to review full report at Codecov.
|
ui/src/message/WebSocketStore.ts
Outdated
@@ -42,6 +42,8 @@ export class WebSocketStore { | |||
.catch((error: AxiosError) => { | |||
if (error && error.response && error.response.status === 401) { | |||
this.snack('Could not authenticate with client token, logging out.'); | |||
} else { | |||
this.snack('Lost network connection, please refresh the page.'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this only displays once, right? So the user would have no idea that it is no longer connected to the server once he missed the initial notification. Can we schedule a reconnect here? Or at least add a persistent/repeating notification so that users can't miss it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added a banner with a retry button.
18f7a7f
to
727a515
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fantastic:)
727a515
to
0596674
Compare
No description provided.