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>
139 lines
4.6 KiB
TypeScript
139 lines
4.6 KiB
TypeScript
import type { Torrent } from '../shared';
|
|
import { useEffect, useState } from 'react';
|
|
import { X } from 'lucide-react';
|
|
import { Button } from '@/components/ui/button';
|
|
import {
|
|
Dialog,
|
|
DialogContent,
|
|
DialogDescription,
|
|
DialogFooter,
|
|
DialogHeader,
|
|
DialogTitle,
|
|
} from '@/components/ui/dialog';
|
|
import { Input } from '@/components/ui/input';
|
|
import { Label } from '@/components/ui/label';
|
|
import { useTorrentMutations } from '../useTransmissionData';
|
|
|
|
// torrent-set replaces the whole labels array — there is no add/remove verb — so editing labels across a
|
|
// multi-selection means deciding what "the labels" are for a set that may not agree. The dialog seeds from
|
|
// the intersection and warns when the selection is not uniform, rather than silently flattening it.
|
|
|
|
type LabelsDialogProps = {
|
|
open: boolean;
|
|
onOpenChange: (open: boolean) => void;
|
|
targets: Torrent[];
|
|
/** Labels already in use anywhere, for one-click reuse. */
|
|
known: string[];
|
|
};
|
|
|
|
export const LabelsDialog = ({ open, onOpenChange, targets, known }: LabelsDialogProps) => {
|
|
const { set } = useTorrentMutations();
|
|
const [labels, setLabels] = useState<string[]>([]);
|
|
const [draft, setDraft] = useState('');
|
|
|
|
const uniform =
|
|
targets.length <= 1 ||
|
|
targets.every((t) => [...t.labels].sort().join(' |