pastilhasandClaude Opus 5
f8028364f1
Sixth extraction, straight after photos. Everything transmission now lives at gitea.officer.dev/plugins/transmission. Deleted, not commented: the sidecar, the api router, the Transmission app (28 files including detail/ and dialogs/), the screen, the App.tsx route pair, the Dashboard barrel line, the usePageTitle rule, the AppRegistry wiring, the officerdev barrel re-exports, the permission registry entry, the hono.ts import and mount comments, and the app-store catalogue entry. No database change: transmission owns no tables. Its connection lives in service_connections, a core table it now depends on from outside — a real coupling, recorded in the plugin's own PLUGIN.md rather than left to be discovered. ── Test fixtures, repointed rather than deleted ── Transmission was the canonical `members: 'none'` fixture — a single-tenant daemon with no user concept — across three app-store test files. slskd has the identical shape, so the assertions moved there. Deleting them would have quietly dropped coverage of the no-members install path along with the plugin, which is the same trap the vault extraction hit with `members: 'invite'`. ── Vocabulary swept, per the runbook ── Six screens and two App.tsx comments pointed at `/photos` or `/transmission` as the worked example of the Workspace/Panel shape. Both are plugins now, so those pointers dangled at code no longer in the tree. Repointed at /command-hq and /soulseek, which are core. bunx tsgo clean. 1080 pass / 0 fail. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
39 lines
1.8 KiB
TypeScript
39 lines
1.8 KiB
TypeScript
import { Navigate, useParams } from 'react-router';
|
|
import type { LayoutNode } from 'officerdev';
|
|
import { WorkspaceView, DEFAULT_GITEA_SECTION, giteaSectionPath, isGiteaSection } from 'officerdev';
|
|
import { useDashboardState } from 'state/useDashboardState';
|
|
import { defaultLayout } from './defaultLayout';
|
|
|
|
// /gitea uses the Workspace/Panel system (like /command-hq): a section nav on the left and the section view
|
|
// on the right. Both talk to the officer-gitea sidecar through the /api/gitea auth proxy, which holds no
|
|
// Gitea credentials of its own — the instance URL and the access token live in the sidecar.
|
|
//
|
|
// The open section is :section in the URL, so the panels read it with useParams instead of passing state
|
|
// between themselves over a channel. This screen backs both /gitea and /gitea/:section and is the single
|
|
// place that decides what an absent or bogus section means.
|
|
|
|
export const GiteaScreen = () => {
|
|
const { section, owner, name } = useParams();
|
|
const workspace = useDashboardState<LayoutNode>('screens/gitea', defaultLayout);
|
|
|
|
// Bare /gitea, or a section that doesn't exist, resolves to a canonical URL rather than rendering a default
|
|
// while the address bar says something else — the nav highlight is derived from the URL.
|
|
//
|
|
// A repository route (/gitea/repo/:owner/:name/…) has no :section at all and is exempt: it is a second,
|
|
// deeper shape on the same screen, not a malformed section.
|
|
const inRepo = !!owner && !!name;
|
|
if (!inRepo && !isGiteaSection(section)) {
|
|
return <Navigate to={giteaSectionPath(DEFAULT_GITEA_SECTION)} replace />;
|
|
}
|
|
|
|
return (
|
|
<div className="h-full w-full pt-2">
|
|
<WorkspaceView
|
|
workspace={workspace}
|
|
locked
|
|
appTypes={{ allowed: ['gitea-nav', 'gitea-view'], fallback: 'gitea-view' }}
|
|
/>
|
|
</div>
|
|
);
|
|
};
|