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.
16 lines
765 B
TypeScript
16 lines
765 B
TypeScript
import { createContext, useContext } from "react";
|
|
import { type Sub } from "./plexSubUrl";
|
|
|
|
// The read + publish sides of the Plex view bridge (see PlexViewBridge for why it is a bridge), split
|
|
// out of that file so it exports only components (Fast Refresh).
|
|
export type PlexViewControls = {
|
|
kind: Sub["kind"]; // the current top-level plex view — the header controls derive their state from it
|
|
open: (v: Sub) => void;
|
|
};
|
|
|
|
export const PlexViewReadContext = createContext<PlexViewControls | null>(null);
|
|
export const PlexViewPublishContext = createContext<(c: PlexViewControls | null) => void>(() => {});
|
|
|
|
export const usePlexViewControls = () => useContext(PlexViewReadContext);
|
|
export const usePublishPlexView = () => useContext(PlexViewPublishContext);
|