chore: user zustand store for server state#1283
Open
gmaclennan wants to merge 1 commit intodevelopfrom
Open
Conversation
cimigree
approved these changes
Jan 26, 2026
Contributor
cimigree
left a comment
cimigree
left a comment
There was a problem hiding this comment.
I notice this store doesn't use a context wrapper...
Is that because:
Testing this would require mocking the Node.js channel anyway?
Or should this eventually be wrapped in context for consistency?
But in the meantime, nice work reducing boilerplate!
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
2 participants
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 is a non-urgent follow-up to #1279 to switch the implementation to use a zustand store. The functionality should be the same, but this reduces some boilerplate and matches our existing use of Zustand for stores.