pastilhasandClaude Opus 5
417e091dfe
two fixed panels could show two of NPM's seven sections and had nowhere to put the other five. now the left column is the section list — proxy hosts, redirections, streams, 404 hosts, access lists, certificates, connection — and the right renders whichever is chosen. NPM's own vocabulary, in NPM's own order. somebody who has used it should find the same words, and somebody who has not will end up in NPM's UI eventually anyway; better names would just mean learning both. "404 hosts" reads oddly and is theirs, so the hint under it says what it means. the two panels never speak. the nav writes ?section= and the detail pane reads it — navigation-audit's rule, and it is what makes a section linkable and survive a reload. changing section clears ?host=, which belonged to the list that was open. three things folded up while doing it. the unconfigured check moved to the detail pane and happens once, so all seven sections say "no connection yet" the same way instead of six saying it badly. the settings gear is gone: connection is a nav row now. and the four list-only sections are one component, differing only in what a row says — proxy hosts and certificates stay separate because they have real behaviour, and folding them in would be a props bag that is a worse version of both. the counts in the nav are one request each. affordable against a local NPM, and they answer "is this worth opening" without a click. a count that fails is absent rather than zero — zero is a fact about NPM, a failure is a fact about the request, and the detail pane reports that properly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
32 lines
1.6 KiB
TypeScript
32 lines
1.6 KiB
TypeScript
import { List, MessageSquare, PanelRight } from 'lucide-react';
|
|
import type { AppRegistryMeta } from 'officerdev';
|
|
import { NavPanel } from './NavPanel';
|
|
import { DetailPanel } from './DetailPanel';
|
|
import { ChatPanel, ChatPanelHeader } from './ChatPanel';
|
|
|
|
// Three panels: a nav, a detail pane, and a chat.
|
|
//
|
|
// The nav and the detail pane are SIBLINGS that never speak to each other — the nav writes `?section=` and
|
|
// the detail pane reads it. That is `docs/navigation-audit.md`'s rule and it is why the sections are
|
|
// linkable and survive a reload. It replaced a pair of fixed panels (Hosts and Certificates side by side),
|
|
// which could show two of NPM's seven sections and had nowhere to put the other five.
|
|
//
|
|
// The chat panel has to be OURS even though the chat inside it is the platform's — `PluginScreen` pins the
|
|
// layout to `allowed = panels.map(p => p.key)`, so naming `officerdev/chat` in layout.ts renders the
|
|
// fallback instead. See ChatPanel.tsx.
|
|
//
|
|
// `availableOnPanel: false` — these belong to this plugin's screen, not to the generic panel picker.
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{ key: 'proxy-manager-nav', name: 'Sections', icon: List, component: NavPanel, availableOnPanel: false },
|
|
{ key: 'proxy-manager-detail', name: 'Detail', icon: PanelRight, component: DetailPanel, availableOnPanel: false },
|
|
{
|
|
key: 'proxy-manager-chat',
|
|
name: 'Chat',
|
|
icon: MessageSquare,
|
|
component: ChatPanel,
|
|
// The conversation picker, scoped to this plugin's own chat directory.
|
|
header: ChatPanelHeader,
|
|
availableOnPanel: false,
|
|
},
|
|
];
|