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
docs: untrack snapshot only when the value is never downstream of async - #1711
Follow-up to #1710. A top-level untrack snapshot is only safe when the value is never downstream of async: an async-derived value can still be pending (the read throws) or mid-transition (the snapshot is the old committed value), and a component rarely knows where its props come from.
concepts/reactivity and migration/from-solid-1: the snapshot guidance adds that condition.
Requested by Ryan · project thread
Description(required)
Follow-up to #1710. A top-level
untracksnapshot is only safe when the value is never downstream of async: an async-derived value can still be pending (the read throws) or mid-transition (the snapshot is the old committed value), and a component rarely knows where its props come from.concepts/reactivityandmigration/from-solid-1: the snapshot guidance adds that condition.reference/solid-js/untrackanddiagnostics/strict-read-untracked: regenerated withsync:ref/sync:diagnosticsfrom the docs: untrack snapshot only when the value is never downstream of async solid#5053 branch (only these two pages;source_refstaysmain).lint:toneshows no new findings;prettier --checkpasses. Merge after solidjs/solid#5053.Related issues & labels
Generated by Claude Code