Skip to content

Commit 982be38

Browse files
committed
docs(signals): F-5's one exception, the Errored recovery re-arm (D-39)
Approved wording (maintainer, 2026-11-02). Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE
1 parent d631d3c commit 982be38

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎packages/signals/docs/RULES-FUNDAMENTALS.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ These are the only words the fundamentals use. Internal names (transaction, stag
7272

7373
## F-5. A disarmed boundary forwards: it keeps its content and holds like any reader, until `on` arms it again
7474

75-
**Immutable.** Once a `<Loading>` has shown content it is disarmed: a later refetch or hold does not send it back to its fallback — it keeps the content, and the pending render effects under it are forwarded into the change's hold exactly as if they were read in the open (F-2). The only way back is `on` — a dependency list: a change to anything `on` reads arms the boundary again (F-4), so the render effects under it leave the hold they were forwarded into and the boundary shows its fallback, with the change's frame, until the new content is ready; if nothing under it is pending, nothing happens. The value `on` returns is never compared, and the children are not re-created — they stay alive behind the fallback. A lane is that same hold: the async under a disarmed boundary is forwarded into it, so a display-ahead value and the content move together, exactly as they would with no boundary there.
75+
**Immutable.** Once a `<Loading>` has shown content it is disarmed: a later refetch or hold does not send it back to its fallback — it keeps the content, and the pending render effects under it are forwarded into the change's hold exactly as if they were read in the open (F-2). The only way back is `on` — a dependency list: a change to anything `on` reads arms the boundary again (F-4), so the render effects under it leave the hold they were forwarded into and the boundary shows its fallback, with the change's frame, until the new content is ready; if nothing under it is pending, nothing happens. One exception (D-39): behind a shown error fallback nothing is on screen, so a `<Loading>` there has not shown content — the error boundary's recovery re-arms it, and it catches what is still pending in the replacement frame as on a first load (ruled 2026-11-02, #4627). The value `on` returns is never compared, and the children are not re-created — they stay alive behind the fallback. A lane is that same hold: the async under a disarmed boundary is forwarded into it, so a display-ahead value and the content move together, exactly as they would with no boundary there.
7676

7777
**What it does not say.** It does not say the fallback of a re-arm appears _ahead_ of the change that caused it (F-7: it lands with that change's frame). It does not say a re-arm paints its fallback while its frame waits on the same data read outside the boundary. The boundary is armed; the screen stays on the old content until that hold lifts (D-16).
7878

0 commit comments

Comments
 (0)