You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ac28157
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): optimistic store guesses survive re-asks, answer latest() and stay per-action (#4329) (#4330)
* fix(signals): a per-key optimistic guess survives a re-ask landing while its action is pending (#4329)
A derive that writes a keyed list through its draft (`d.length = 0;
d.push(...rows)`, or `d.issues = rows`) replaced the guessed row with a
fresh object, so the guess, which lives on the old row's target, left the
screen before its action settled. The draft's new object at a guessed
row's slot (by key in a keyed list) is now adopted by that row's target,
as a reconcile landing already does: the guess stays until the commit
(D-34) and guesses on other rows stay independent (D-33).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
* fix(signals): optimistic store corrections answer latest() and keep actions independent (#4329)
- The draft path's pairing reuses reconcile: the container above a
guessed row reconciles the new object at its slot, so both landing
paths share one keyed pairing and one leaf diff.
- reconcile judges a key under a guess against the guess too, so a
truth equal to the covered value still answers it: latest() reads
the truth, the screen keeps the guess until the commit (D-34).
- supersede no longer joins the landing's tick to the parent hold; the
parent takes the node, and passes deriving from the held truth join
on their own. One re-ask answering two actions' guesses no longer
ties them together (D-33).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
* chore(size): raise the store scenario cap for #4329's fix
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
---------
Co-authored-by: Claude <[email protected]>
A per-key guess on `createOptimisticStore` stays on screen through a re-ask that lands while its action is pending (D-34, #4329). When the derive writes a keyed list through its draft (`d.length = 0; d.push(...rows)`, or `d.issues = rows`) under a row that carries a guess, the new object at that row's slot is reconciled into the guessed row, as a returned landing is: the row keeps its proxy and the screen shows the guess until the action commits.
6
+
7
+
On both landing paths, a guessed key is judged against its guess, so `latest()` answers the truth even when the truth equals the value the guess covered. A correction or confirmation no longer joins the whole landing to the guess's hold. When one re-ask answers guesses from two actions, they stay independent (D-33): each row reverts or commits when its own action settles, and rows with no guess show their new truth at the landing.
0 commit comments