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>
44 lines
1.6 KiB
TypeScript
44 lines
1.6 KiB
TypeScript
import type { PluginManifest } from '@@/plugins/manifest';
|
|
|
|
/**
|
|
* Transmission — the torrent daemon you already run, driven from Officer.
|
|
*
|
|
* ── What this plugin is, and what it is not ──
|
|
*
|
|
* It does not install or supervise Transmission, and it holds no torrents. You point it at a daemon's
|
|
* RPC endpoint and it speaks that protocol on your behalf, holding the credentials server-side so no
|
|
* device carries them.
|
|
*
|
|
* ── Where the connection lives ──
|
|
*
|
|
* In `service_connections`, a CORE table — this plugin declares no schema of its own. That is deliberate
|
|
* rather than an omission: the table is the app store's shared credential store, keyed by
|
|
* `(user_id, service)`, already encrypted at rest and already read by `app-store/effects.ts`. Giving
|
|
* transmission a private copy of the same three columns would be a second place the same fact could live.
|
|
*
|
|
* It does mean this plugin depends on a core facility it does not own. Recorded in PLUGIN.md rather than
|
|
* hidden, because it is the one thing about this extraction that is not self-contained.
|
|
*
|
|
* ── No `osDependencies` ──
|
|
*
|
|
* Nothing shells out. The sidecar speaks Transmission's JSON-RPC over `fetch`.
|
|
*/
|
|
export const manifest: PluginManifest = {
|
|
publisher: 'officerdev',
|
|
version: '1.0.0',
|
|
platform: '>=1.0.0',
|
|
|
|
label: 'Transmission',
|
|
summary: 'Torrent downloads — queue, files, peers and speed, from your own daemon',
|
|
icon: 'Download',
|
|
color: '#dc2626',
|
|
|
|
permissions: [
|
|
{
|
|
key: 'transmission',
|
|
label: 'Transmission',
|
|
description: 'Torrent downloads',
|
|
},
|
|
],
|
|
};
|