Skip to content

Updated user Profile - #2

Merged
smarcet merged 1 commit into
mainfrom
feature/allow_chat_with_me
Sep 20, 2021
Merged

Updated user Profile#2
smarcet merged 1 commit into
mainfrom
feature/allow_chat_with_me

Conversation

@smarcet

@smarcet smarcet commented Sep 20, 2021

Copy link
Copy Markdown
Collaborator

Added public_profile_allow_chat_with_me
Updated token introspection response

Signed-off-by: smarcet@gmail.com smarcet@gmail.com
Change-Id: Ib22b674605e469f52d582b5e6e62a0b42c00c6ae

Added public_profile_allow_chat_with_me
Updated token introspection response

Signed-off-by: smarcet@gmail.com <smarcet@gmail.com>
Change-Id: Ib22b674605e469f52d582b5e6e62a0b42c00c6ae
@smarcet
smarcet merged commit 5132ea1 into main Sep 20, 2021
smarcet added a commit that referenced this pull request Sep 30, 2021
Added public_profile_allow_chat_with_me
Updated token introspection response

Signed-off-by: smarcet@gmail.com <smarcet@gmail.com>
Change-Id: Ib22b674605e469f52d582b5e6e62a0b42c00c6ae
smarcet added a commit that referenced this pull request Jul 23, 2026
Both cancel paths (resetToPasswordFlow and handleDelete) reset the UI
optimistically and fired cancelLogin() without handling failure beyond a
console.error - on a network failure the server-side pending challenge
silently survived until its 300s TTL while the UI told the user it was
cancelled.

Extract the duplicated call into a single cancelPendingLogin() helper
that warns the user via the existing snackbar when the server-side
invalidation fails, so they know the pending verification will only die
by its own TTL. The optimistic reset is kept - the user asked to cancel,
so returning control immediately stays correct.

PR #142 review finding LOW #2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant