meta: use zustand for persistant state #202
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
sehyunc
changed the title
sehyunc
force-pushed
the
sehyun/zustand-persist-client
branch
from
461dde4 to
81a635f
Compare
sehyunc
force-pushed
the
sehyun/zustand-persist-client
branch
from
81a635f to
246eb0e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR migrates persistent storage to zustand
storewithpersistmiddleware from directly mutating cookies and localstorage. This provides a cleaner and more consistent API for getting/setting state. State is split up depending on if it needs to be present at Server Rendering time (ServerState) due to impact on LCP or if it can be hydrated after initial mount (ClientState).