feat: Add client state patterns for context vs store#4
Merged
Conversation
ThomasHartDev
commented
Jul 23, 2026
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.
Same pure cart reducer runs in two hosts on /state-management so you can feel the re-render difference. Context + useReducer (with state and dispatch split) is fine for tree-scoped UI, but any field change notifies every state consumer. The external store uses useSyncExternalStore plus selectors, so typing the note leaves the badge and total alone.
No-op actions return the prior state reference so the store skips notify. When most leaves only need a thin slice, or updates get chatty, that selector path is the better default for now.