peter
c3d88d9b20
The 43 react-refresh/only-export-components warnings the gate let through meant an edit to a provider (or AnchoredPopover, Toaster, plexDetailUi, …) could not be hot-swapped: Fast Refresh reloads a module that also exports hooks or helpers. - Each provider's contexts, the types its hooks return and the hooks themselves live in a sibling context module (navigationContext.ts, channelsContext.ts, …); the provider file keeps the component. loadAccountFilters moved next to the feed filters' defaults (feedFiltersInit.ts), following navigationInit/playlistsInit. - Helpers that sat in component files have their own modules: welcomeMode, downloadTitle, plexPlayable, channelSync, ui/anchoredPopoverHooks, ui/pageToolbarSlot, ui/pagerContent, ui/toastLevels, ui/overlayOrder, ui/tableAlign, lib/plexDetail; the cells of the channel columns and the registry's page wrappers are components files of their own (channelCells, modulePages). - usePersistedTab, an alias of useAccountPersistedState, is gone; its callers use the original. npm run lint is now eslint --max-warnings 0, so a warning fails the gate like an error does.
54 lines
2.4 KiB
TypeScript
54 lines
2.4 KiB
TypeScript
import { useCallback, useMemo, useState, type ReactNode } from "react";
|
|
import { LS, setAccountRaw } from "../lib/storage";
|
|
import { useUrlMirror } from "../lib/useUrlMirror";
|
|
import { useNavigation } from "./navigationContext";
|
|
import { readSelectedId } from "./playlistsInit";
|
|
import {
|
|
PlaylistsActionsContext,
|
|
PlaylistsStateContext,
|
|
type PlaylistsActions,
|
|
type PlaylistsState,
|
|
} from "./playlistsContext";
|
|
|
|
// Owns the Playlists module's shared local state — the rail's name filter and the selected playlist
|
|
// — lifted out of the App god component so the header search box, the PlaylistsRail, and the
|
|
// Playlists detail pane read it via hooks instead of prop-drilling through App. Mirrors
|
|
// FeedFiltersProvider / NavigationProvider (split State + Actions contexts, one-line hooks; composed
|
|
// in main.tsx around <App/>).
|
|
//
|
|
// The `search` term is ephemeral (resets on reload, like the other list filters); the selected
|
|
// playlist is per-account persisted (LS.playlist) so a reload returns you to it. Neither is
|
|
// server-synced, and an account switch does a full reload, so init-from-storage is all the
|
|
// hydration these need — no per-account load effect (unlike the server-backed feed filters).
|
|
//
|
|
// The contexts + hooks live in playlistsContext.ts.
|
|
|
|
export function PlaylistsProvider({ children }: { children: ReactNode }) {
|
|
const [search, setSearchState] = useState("");
|
|
const [selectedId, setSelectedIdState] = useState<number | null>(readSelectedId);
|
|
|
|
const setSearch = useCallback((q: string) => setSearchState(q), []);
|
|
const setSelectedId = useCallback((id: number | null) => {
|
|
setSelectedIdState(id);
|
|
if (id != null) setAccountRaw(LS.playlist, String(id));
|
|
}, []);
|
|
|
|
// Mirror the selected playlist to ?pl on the Playlists page so it's bookmarkable; clear it elsewhere
|
|
// (the localStorage copy still restores it on return). useUrlMirror keeps ?page and the other nav
|
|
// params intact.
|
|
const { page } = useNavigation();
|
|
useUrlMirror({ pl: page === "playlists" && selectedId != null ? String(selectedId) : null });
|
|
|
|
const state = useMemo<PlaylistsState>(() => ({ search, selectedId }), [search, selectedId]);
|
|
const actions = useMemo<PlaylistsActions>(
|
|
() => ({ setSearch, setSelectedId }),
|
|
[setSearch, setSelectedId],
|
|
);
|
|
|
|
return (
|
|
<PlaylistsActionsContext.Provider value={actions}>
|
|
<PlaylistsStateContext.Provider value={state}>{children}</PlaylistsStateContext.Provider>
|
|
</PlaylistsActionsContext.Provider>
|
|
);
|
|
}
|