Show the account a failed login just saved
The daemon now saves Sneedchat and Matrix accounts before attempting the login, so a failure leaves something to correct and retry. This half was still refreshing the account list only on success, which kept that account invisible - the fix existed and nothing showed it. Refreshed either way now. A failed attempt puts a disconnected account on screen with what was entered, and Connect retries it. Submodule moves to the matching daemon.
This commit is contained in:
1 parent
0473eda368
commit
3ac102ccde
2 files changed
+9
-3
No files matched your search
+1
-1
Submodule nobilis updated: 84d2e09718...6aa50816d7.
@@ -810,7 +810,11 @@ export class ChatStore {
|
||||
break
|
||||
case 'sockChatLoginResult':
|
||||
this.set({ sockChatLoginStatus: data.error || '' })
|
||||
if (!data.error) void this.refreshAccounts()
|
||||
// Refreshed either way. The daemon now saves the account before it
|
||||
// attempts the login, so a wrong password or a Tor bootstrap that
|
||||
// never finished leaves an account sitting there to correct and
|
||||
// retry - and refreshing only on success was what kept it invisible.
|
||||
void this.refreshAccounts()
|
||||
break
|
||||
|
||||
// Verification is a multi-step flow whose steps all arrive as pushes:
|
||||
@@ -848,7 +852,9 @@ export class ChatStore {
|
||||
break
|
||||
case 'matrixLoginResult':
|
||||
this.set({ matrixLoginStatus: data.error || '' })
|
||||
if (!data.error) void this.refreshAccounts()
|
||||
// Same as Sneedchat above: the account exists before the attempt, so
|
||||
// a failure has something to show and something to retry.
|
||||
void this.refreshAccounts()
|
||||
break
|
||||
|
||||
default:
|
||||
|
||||
Reference in new issue
Block a user