solidjs / solid / 41408616582

78%

main: 89%

push

github

test: pin `Loading on` after an action-held input change (#4605) (#4609)

A keyed optimistic list asked by `filter()`; an action guesses, yields, then
refreshes; a `filter` write while the action is out is held with it (D-34,
#4336). After everything rests, a second `filter` write with nothing in
flight arms `<Loading on={filter()}>` and shows the fallback with that
change's frame (F-5, D-15). Without `on` the shown boundary forwards and the
change holds the old list until the answer (F-5).

Current `next` already behaves this way, in dev and prod conditions and with
both compilers: the issue's reported frames have the two cases swapped. These
pins (the issue's web spec with asserted frames, plus a signals-only twin)
keep it so.


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

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

803 of 1104 branches covered (72.74%)

Branch coverage included in aggregate %.

1131 of 1369 relevant lines covered (82.62%)

29.9 hits per line