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.
20 lines
654 B
TypeScript
20 lines
654 B
TypeScript
import { createContext, useContext } from "react";
|
|
import type { FeedView } from "../lib/feedView";
|
|
|
|
// The feed view-mode contexts + hooks, split out of FeedViewProvider so that file exports only
|
|
// components (Fast Refresh).
|
|
|
|
export interface FeedViewActions {
|
|
setView: (v: FeedView) => void;
|
|
}
|
|
|
|
export const FeedViewStateContext = createContext<FeedView>("cards");
|
|
export const FeedViewActionsContext = createContext<FeedViewActions>({ setView: () => {} });
|
|
|
|
export function useFeedView(): FeedView {
|
|
return useContext(FeedViewStateContext);
|
|
}
|
|
export function useFeedViewActions(): FeedViewActions {
|
|
return useContext(FeedViewActionsContext);
|
|
}
|