pastilhasandClaude Opus 5
864dd16355
The sixth plugin out, immediately after photos. A sidecar, a proxy router and 29 web files; no db/ directory, because there are no tables. ── The one thing that is not self-contained ── The connection lives in `service_connections`, a CORE table, reached through getServiceConnection/saveServiceConnection/getServiceCredentials. This plugin declares no schema. Deliberate: that table is the app store's shared credential store, keyed on (user_id, service), already encrypted at rest and already read by app-store/effects.ts. A private copy of the same three columns would be a second place the same fact could live, and the runbook is explicit that a move plus a data-format change gives any failure two causes. The cost, stated rather than hidden: this plugin depends on a core facility it does not own, and would break if that table changed shape. Photos, by contrast, owns photos_config outright. ── 38 palette classes paid down, mapped by meaning ── blue downloading / download speed -> info cyan checking (verifying) -> busy emerald seeding / complete -> success amber queued / stalled / warnings -> warning Collapsing blue and cyan into one tone would have lost a real distinction in the status dot, so `checking` went to `busy` — in-progress work, which is what that tone is for. ── A near-miss worth recording ── The first copy globbed *.tsx and *.ts and silently missed detail/ and dialogs/ — ten components. tsgo caught it as ten "cannot find module" errors. Worth stating because it is quiet in the other direction: had those been imported lazily, the typecheck would have passed and the panels would have broken at runtime. Check the directory tree, not the file glob. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
30 lines
1.0 KiB
TypeScript
30 lines
1.0 KiB
TypeScript
import { useServiceConnection } from 'officerdev';
|
|
import { useTransmissionSection } from './useTransmissionSection';
|
|
import { TorrentsView } from './TorrentsView';
|
|
import { StatsView } from './StatsView';
|
|
import { SettingsView } from './SettingsView';
|
|
import { ConnectionView } from './ConnectionView';
|
|
|
|
// Right panel of the /transmission workspace — renders the section named by the URL.
|
|
//
|
|
// With no daemon configured every other section can only render an error, so the connection form takes over
|
|
// until there is one. The URL is left alone: once connected, the section already in it is what appears.
|
|
|
|
export const TransmissionView = () => {
|
|
const section = useTransmissionSection();
|
|
const { data, isLoading } = useServiceConnection('transmission');
|
|
|
|
if (!isLoading && !data?.configured) return <ConnectionView />;
|
|
|
|
switch (section) {
|
|
case 'connection':
|
|
return <ConnectionView />;
|
|
case 'stats':
|
|
return <StatsView />;
|
|
case 'settings':
|
|
return <SettingsView />;
|
|
default:
|
|
return <TorrentsView />;
|
|
}
|
|
};
|