github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #349] optimistic update #16861

New Issue
Closed
opened 2026-04-15 14:50:53 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 14:50:53 -05:00
Owner
Copy Link

Originally created by @darklight9811 on GitHub (Oct 26, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/349

Is your feature request related to a problem? Please describe.
When you logout (using react), you wait for the request to finish to update the UI. It would be better for the user experience if we removed the cookies and already updated the ui.

Describe the solution you'd like
Don't wait for the logout request to the backend to happen, update the UI before that happens.

Describe alternatives you've considered
none

Originally created by @darklight9811 on GitHub (Oct 26, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/349 **Is your feature request related to a problem? Please describe.** When you logout (using react), you wait for the request to finish to update the UI. It would be better for the user experience if we removed the cookies and already updated the ui. **Describe the solution you'd like** Don't wait for the logout request to the backend to happen, update the UI before that happens. **Describe alternatives you've considered** none
GiteaMirror added the locked label 2026-04-15 14:50:53 -05:00
GiteaMirror commented 2026-04-15 14:50:55 -05:00
Author
Owner
Copy Link

@luksch42 commented on GitHub (Oct 29, 2024):

While optimistic updates are excellent for non-critical actions, logging out is a security-sensitive event. Updating the UI before confirming the logout could lead to misunderstandings if the session isn't properly terminated on the server side. To ensure user security, imo it's best to update the UI only after the backend confirms the logout.

If you still need optimistic updates, you could implement that directly in your frontend.

<!-- gh-comment-id:2445209114 --> @luksch42 commented on GitHub (Oct 29, 2024): While optimistic updates are excellent for non-critical actions, logging out is a security-sensitive event. Updating the UI before confirming the logout could lead to misunderstandings if the session isn't properly terminated on the server side. To ensure user security, imo it's best to update the UI only after the backend confirms the logout. If you still need optimistic updates, you could implement that directly in your frontend.
GiteaMirror commented 2026-04-15 14:50:56 -05:00
Author
Owner
Copy Link

@darklight9811 commented on GitHub (Oct 30, 2024):

@luksch42 how could I do that? the better-auth has the single source of truth for the user and session, are you talking about encapsulating that information so I can do this implementation through it?

<!-- gh-comment-id:2445734136 --> @darklight9811 commented on GitHub (Oct 30, 2024): @luksch42 how could I do that? the better-auth has the single source of truth for the user and session, are you talking about encapsulating that information so I can do this implementation through it?
GiteaMirror commented 2026-04-15 14:50:56 -05:00
Author
Owner
Copy Link

@luksch42 commented on GitHub (Oct 30, 2024):

@darklight9811 #365 exposes the client store. You should be able to manipulate the data there. The PR has not been merged yet, but work on it is already in progress.

update: merged in v0.6.3-beta.1 :)

<!-- gh-comment-id:2446075512 --> @luksch42 commented on GitHub (Oct 30, 2024): @darklight9811 #365 exposes the client store. You should be able to manipulate the data there. The PR has not been merged yet, but work on it is already in progress. update: merged in [v0.6.3-beta.1](https://github.com/better-auth/better-auth/releases/tag/v0.6.3-beta.1) :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#16861
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?