solidjs / solid / 40779817444

78%

main: 89%

push

github

fix(signals): a Loading armed by latest() leaves its fallback when a second flight held the frame (#4391)

A Loading boundary armed by `on: () => latest(id)` shares `id` with a
second boundary, each over its own async memo of `id`. When the armed
boundary's flight landed while the other's still held the frame, the
output's pass left the verdict lane inside the held transaction's flush
with an answer equal to its committed value: the equality gate notified
nobody, `laneStage` set no LEFT_SHOWN (the frame still blocked) and
cleared the node's lane transaction, so nothing re-ran the reader when
the frame landed — the fallback stayed for good.

A pass leaving a shown lane while its frame is still held now hands the
shown value to `_value` (what the screen shows stays the screen until the
landing, as `dissolveLane` keeps a shown lane's): the answer is a change
against what is seen, staged with the frame, and lands with it.

Paid for by golfing `inFlight` (truthiness, no `!== 0` / `=== true`):
-4 B minified on every verdict bundle.


Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

Co-authored-by: Claude <noreply@anthropic.com>

790 of 1084 branches covered (72.88%)

Branch coverage included in aggregate %.

1125 of 1355 relevant lines covered (83.03%)

30.1 hits per line