mirror of
https://github.com/TanStack/router.git
synced 2026-11-16 19:38:07 +00:00
On Solid's dev and observe builds the match publish inside startTransition is wrapped in OBSERVE.attribution.withOrigin: the ref names the destination route (fullPath, params, to/from pathnames) and dates from the history change that started the load, so the record spans the loader wait even though the publish comes after it. The pending offer, the initial load and same-location reloads are published undeclared. Production is unchanged (OBSERVE is undefined). Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
616 B
616 B
| @tanstack/solid-router |
|---|
| patch |
Declare navigations to Solid's observe tier. On Solid's dev and observe builds (OBSERVE defined), the match publish inside startTransition is wrapped in OBSERVE.attribution.withOrigin with the destination route's fullPath, params, to/from pathnames and at from the history change that started the load, so the holds and re-runs a navigation causes are named after the route and the record spans the loader wait. The pending offer, the initial load and same-location reloads are published undeclared. Nothing changes in production, where OBSERVE is undefined.