peter
5346efcd10
With Settings -> Appearance -> Startup turned off, every NEW tab or window still opened on Home; only a same-tab reload honoured it. The provider tree mounted before /api/me answered, so NavigationProvider's initializer could not read the per-account opt-out, landed on Home and mirrored ?page=home into the address bar. When App pinned the account a moment later, the re-hydrate re-read that mirror and stayed on Home. The same mount-then-patch shape made a new tab start on default filters, the default theme and the browser language, and correct each after the first paint. BootGate (main.tsx, above the providers) now owns the setup-status and /api/me queries and mounts the tree only once the identity is settled: it pins the tab's account and adopts the account's language in a layout effect, so the first frame of the app is already right. The tree is keyed on the account id, which makes "per-account state is read once, for this account" a structural guarantee. With that, the whole re-hydrate machinery is gone: useAccountRehydrate, the reactive active-account store, the markDirty guards, the pin-deferred saved-view seed and the present-dimension bookkeeping of the shared Channels/Plex links. PrefsProvider, FeedFiltersProvider, usePref and App's panel layouts seed from the me cache instead of adopting it in an effect; the theme is applied in layout effects. The app chunk is fetched in parallel with the probe, and the boot screen only fades its label in after 400 ms, on one clock across the gate and the Suspense fallback. Module switches no longer flash a placeholder either. Measured frame by frame in Chromium and WebKit, every first visit to a module showed "Loading..." for 17-70 ms: the lazy chunk's Suspense fallback, then often the first fetch's LoadingState. Pages are now lazyWithPreload components, and App fetches the chunks of every module the account can reach (plus the channel page) once the first page is idle; a preloaded page renders synchronously and never suspends. LoadingState, the one shared loading visual, fades in only after 300 ms, so a fast load shows nothing in between and a slow one still gets its spinner.
25 lines
946 B
TypeScript
25 lines
946 B
TypeScript
import { useCallback, useState } from "react";
|
|
import { getAccountRaw, setAccountRaw } from "./storage";
|
|
import { hydrateSort, type SortOption, type SortState } from "./columnSort";
|
|
|
|
// The per-account persisted sort state, hydrated + healed against the current options — the plumbing
|
|
// the channel manager and channel discovery each hand-rolled (useState + parseSortState + a persist
|
|
// key). One home so a new sortable surface (Plex, a future table) gets persistence for free.
|
|
export function useSortState(
|
|
storageBase: string,
|
|
options: SortOption[] = [],
|
|
fallback: SortState = null,
|
|
): [SortState, (next: SortState) => void] {
|
|
const [sort, setSort] = useState<SortState>(() =>
|
|
hydrateSort(getAccountRaw(storageBase), options, fallback),
|
|
);
|
|
const set = useCallback(
|
|
(next: SortState) => {
|
|
setSort(next);
|
|
setAccountRaw(storageBase, JSON.stringify(next));
|
|
},
|
|
[storageBase],
|
|
);
|
|
return [sort, set];
|
|
}
|