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
Commit 1b9f266
Browse filesBrowse the repository at this point in the historyBrowse files
From the multi-agent review of the @rangojs/router/testing surface (+ external T8):
- runMiddleware now returns `stateCookieName` (parity with runInRequestContext /
runLoaderResult / renderHandler; it accepted `stateCookie` but never surfaced
the resolved name). +3 tests (invalidate/keep/seed).
- runLoaderResult envelope field `data` -> `result`, matching runInRequestContext's
envelope (the two snapshot primitives now agree). Tests + docs updated.
- expectParity: snapshot() gains `.first()` + `.catch(()=>null)` (parity with
readObserved — no unhandled rejection on a missing testid); settleSubmit warns
(instead of silently snapshotting) when the observed state never stabilizes.
- T8: createTestRequestContext().ctx.reverse is typed via the new
TestRequestContextObject so reversing a LOCAL routeMap name type-checks (was
typed against the global Rango.GeneratedRouteMap, forcing a cast). +1 test.
- dispatch: +_rsc_action redirect-interception test (204 + X-RSC-Redirect).
- render-route: +handles-persist-across-navigate, +locale-mount (include('/:locale?'))
tests. cache-status: route-name keys + a mixed-stream filterCacheDecisions test.
installed-vitest-config: assert the bare @rangojs/router -> index.rsc.ts alias.
headersToObject stays duplicated between render-handler (flight tier) and
internal/context (node tier) on purpose — context.ts is not react-server-safe
(why seed-vars was split out); documented in-code.
0 commit comments