solidjs / solid / 41081552755

78%

main: 89%

push

github

docs(signals): try/catch around a reactive read is not a channel (D-42, S-47)

Ruled 2026-10-30. A read's throw — NotReadyError or an error — is addressed
to the graph, not to the code around the read. A dependent of a source that
goes pending or errored is marked with the status and not run (the status
rides the edge so dependents are not re-executed just to re-throw), so a
catch around the read is bypassed on that change and fires only on a pass
that happens to run while the source is already in that state. When it does
fire it severs the channel: the first load is masked, the error never
reaches <Errored>, and the server build never retries.

F-12 amended with the sentence; D-42 states the rule, what is supported
instead (isPending, latest, the boundaries, the effect error arm, try/catch
in action bodies), and what it does not say (no diagnostic today — open).
S-47 is the worked screen for both the pending and the error twin; the
bypass is pinned as it is in tests/try-catch-reactive-read.test.ts.

Co-authored-by: Cursor <cursoragent@cursor.com>

790 of 1090 branches covered (72.48%)

Branch coverage included in aggregate %.

1125 of 1362 relevant lines covered (82.6%)

29.94 hits per line