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 b27247e
Browse filesBrowse the repository at this point in the historyBrowse files
test(router): e2e and consumer coverage for the app version of location state (#994)
Both apps, dev and production, through shared bodies in tests/shared-e2e:
- state another app version stored reads as no state after a reload, typed
and plain, with a clean hydration; a reload under the same version keeps it.
"Another build is running" is modelled by rewriting the version the entry
records (or removing it, an entry from before the record existed).
- back/forward to an entry another version wrote reads no state, without a
document load.
- a slot whose value validate rejects reads as no state (kept apart from the
version cases so it goes with the option if that is removed).
The grid fixture now has a typed reader, a plain-state reader and a validated
one; its `VersionedGrid` definition is `GridState`, without options.
Dev only, in the local loader-hmr suite: an RSC edit bumps the app version in
the running page, the page keeps its location state, and the next document
load drops it.
cloudflare-basic's dogfood test covers the same through renderRoute and
runMiddleware: seeds read back without a version, and a middleware's
locationState carries none.
0 commit comments