pastilhasandClaude Opus 5
6e54f223e6
was `/todos` in the platform: a board, an API and a tree reader pointed at `resolve(process.cwd(), 'todo')`. that is not a setting — it is the belief that there is one project and it is the one the server happens to have been started in. THE READER CAME ACROSS UNCHANGED except for that one line. the frontmatter parser that never rewrites a body, the ordering, the index writer — all of it as it was, and its 8 tests came too and still pass. everything that changed is that the directory is now a parameter. `writeIndex` no longer writes to `process.cwd()` either. that was the same assumption wearing a different hat, and with two projects it would have had every board overwriting one file. the map goes beside the folder it describes. A PROJECT IS A NAME AND A PATH, and paths are confined to the owner's home by the same three checks av-club uses — absolute, realpath BEFORE the containment test, and `root` or `root + sep` rather than a bare startsWith. spelled out again rather than cross-referenced, because the next person to add a path-taking route reads the file they are in. it stores NO ITEMS. one table, a list of folders. uninstalling with "delete its data" ticked loses the list and never a line of anybody's work — which is the property the markdown format was chosen for. `/projects` is owner-only: pointing this at a directory is a statement about the filesystem. moving a card is not, so a member granted `kanban` can work any board they can see. removing a project removes the ROW. the route says so in its response and the button says so in its tooltip, because "delete" beside a folder full of somebody's work should not be ambiguous. README records the seam honestly: the platform keeps its own todo/ and its CLI, so there are two copies of the reader and they will drift. the alternative was making the platform's own backlog depend on a plugin being installed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
31 lines
1.0 KiB
TypeScript
31 lines
1.0 KiB
TypeScript
import type { AppRegistryMeta } from 'officerdev';
|
|
import { FolderTree, SquareKanban } from 'lucide-react';
|
|
import { ProjectsPanel } from './ProjectsPanel';
|
|
import { BoardPanel } from './BoardPanel';
|
|
|
|
/**
|
|
* Two panels: which project, and the board of it.
|
|
*
|
|
* Siblings that never speak to each other — the selector writes `?project=` and the board reads it.
|
|
* That is `docs/navigation-audit.md`'s rule, and it is what makes a board linkable and survive a reload.
|
|
*
|
|
* `availableOnPanel: false` on the selector: a project list on somebody's dashboard would be a list
|
|
* that changes a URL parameter nothing on that screen reads. The BOARD is offered, because a board of
|
|
* the project you last chose is a perfectly good dashboard panel.
|
|
*/
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{
|
|
key: 'kanban-projects',
|
|
name: 'Projects',
|
|
icon: FolderTree,
|
|
component: ProjectsPanel,
|
|
availableOnPanel: false,
|
|
},
|
|
{
|
|
key: 'kanban-board',
|
|
name: 'Board',
|
|
icon: SquareKanban,
|
|
component: BoardPanel,
|
|
},
|
|
];
|