Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/router-lifecycle-use-routeid
7e2f3ede ci: apply automated fixes
5 hours ago by autofix-ci...
Succeeded
fix/router-lifecycle-use-routeid
67b717a2 test(router-core): consolidate /foo loaderDeps router setup into createFooRouter helper
5 hours ago by sleitor
Succeeded
fix/router-lifecycle-use-routeid
e17d44aa fix(router-core): separate cache identity (match.id) from lifecycle hook identity (routeId) Cache entries use match.id (routeId + params + loaderDeps) so navigating between different params/deps correctly caches the previous match. Lifecycle hooks (onEnter/ onStay/onLeave) use routeId to track route *presence* in the matched tree — so navigating /posts/123 → /posts/456 fires onStay for /posts/$id, not onLeave+onEnter. Addresses caching regression spotted by @Sheraff in PR #6772 test.
7 hours ago by sleitor
Succeeded
fix/router-lifecycle-use-routeid
2935413e ci: apply automated fixes
1 day ago by autofix-ci...
Succeeded
fix/router-lifecycle-use-routeid
f5e92d7e fix(router-core): use routeId for lifecycle hooks to fix onStay with loaderDeps When loaderDeps change (e.g. from search param updates), the match.id changes because it includes the loaderDepsHash. This caused the lifecycle hooks (onLeave/onEnter/onStay) to compute exiting/entering/staying matches using match.id, which treated a loaderDeps change on the same route as 'leave + re-enter' instead of 'stay'. Fix: use match.routeId (consistent with loader's cause param logic) when computing exitingMatches, enteringMatches, and stayingMatches so that only an actual route change triggers onLeave/onEnter. Fixes #6765
1 day ago by sleitor