Merged
Conversation
commit: |
onmax
force-pushed
the
fix/update-user-persist
branch
3 times, most recently
from
9431e6f to
73765b3
Compare
onmax
force-pushed
the
fix/update-user-persist
branch
from
48f8f10 to
7e88a4f
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #108
Problem
updateUser()only patched local reactive state, so changes were lost on session refresh because nothing was persisted to the server.Behavior
updateUser()persists withclient.updateUser(updates).updateUser()only patches local state.Repros
nuxt-better-auth-108nuxt-better-auth-108-fix