fix: track nested deep optimistic store pending state#2748
Merged
ryansolid merged 2 commits intoJun 7, 2026
Conversation
🦋 Changeset detectedLatest commit: e17633c The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Fixes #2718
Fix: Nested
deep(optimisticStore)Pending StateProblem
isPending(() => deep(optimisticStore))stayedfalseduring an optimistic transition when the optimistic write happened inside a nested object or array.Example:
In this case, the optimistic value was visible immediately, but
isPending(() => deep(store))did not becometrueuntil a laterrefresh().Root Cause
deep()usessnapshotImpl()to recursively traverse a store and subscribe to every nested store node.When
snapshotImpl()found a store proxy, it reset the proxy lookup map to the global store lookup:That works for regular stores, but optimistic stores use their own
STORE_LOOKUPmap for nested proxies.Because the traversal switched back to the global lookup, nested optimistic objects could be traversed as plain data instead of through their optimistic store proxies. As a result,
isPending()did not collect the nested pending source.Fix
Preserve the current store's lookup map when one exists:
This keeps nested traversal inside the optimistic store's proxy graph, allowing
deep()to read the nested optimistic nodes and allowingisPending()to observe their pending state immediately.