mirror of
https://github.com/PerpetualSoftware/pad.git
synced 2026-09-25 03:42:06 +00:00
xarmian
74ccada739
Final review round 4, on error and empty paths.
A hung metadata HEAD produced no rejection, so nothing downstream ever
fired: the panel sat on "Reading details…" forever with no Retry, which
to a user is indistinguishable from a hang and is the exact
loading-vs-failed confusion DR-10 exists to prevent. It now calls a read
that has not settled in 10s a failure — without aborting it, so a slow
answer that does arrive still corrects the error state.
A blank filename rendered as a blank tile, an accessible name that said
nothing, and a confirmation reading "Delete ?" — the one place it
matters, because the user is being asked to approve destroying something
the prompt cannot name. One `displayFilename` helper now, used by the
strip, the panel and both delete prompts; the panel's own "Attachment"
fallback is gone, since two words for one nameless thing is how the
surfaces drift.
Declined, with reasons recorded at the sites:
- The body editor snapshots its workspace at mount, which the review read
as staleable. It is not: both <Editor> mounts sit inside `{#key
item.id}`, and a workspace switch necessarily lands on a different
item. Noted in the code, because the safety comes from the key rather
than from anything visible at the snapshot.
- A download 403 has no in-app error path. Download is a real anchor by
DR-16 — the server sends an inline disposition for most types, so a
fetch-and-blob would stop it being a download. The browser's own
response is the honest surface.
Also corrects the `workspaceSlug` option comments in both extensions,
which described behaviour the previous round moved to the address reader.
Pad Web UI
SvelteKit 2 + Svelte 5 frontend for Pad, compiled to static files and embedded into the Go binary.
Development
npm install
npm run dev # Dev server at localhost:5173 (proxies API to localhost:7777)
npm run build # Production build to build/
npm run check # Type checking with svelte-check
When developing, run the Go backend separately with make dev from the project root.
Building for Production
Do not build in isolation. Always use make build from the project root — this builds the web frontend, then compiles the Go binary with the build output embedded via //go:embed.
Stack
- Svelte 5 with runes (
$state,$derived,$effect) - SvelteKit 2 with
adapter-static(SPA mode) - Tiptap block editor with markdown round-trip
- svelte-dnd-action for drag-and-drop in board/list views
- SSE for real-time updates
- TypeScript throughout
Structure
src/
routes/ SvelteKit pages
+layout.svelte App shell (sidebar + main)
+page.svelte Landing/redirect
[workspace]/
+page.svelte Dashboard (collections, phases, activity)
+layout.svelte SSE connection per workspace
[collection]/
+page.svelte Collection view (board/list)
[collection]/[item]/
+page.svelte Item detail + editor
conventions/ Purpose-built conventions page
playbooks/ Purpose-built playbooks page
settings/ Workspace settings
lib/
api/client.ts HTTP API client
components/
layout/ Sidebar, navigation
editor/ Tiptap editor, raw markdown editor
fields/ FieldEditor, relation picker
items/ ItemCard, ItemDetail
collections/ BoardView, ListView
common/ StatusBadge, badges, modals
search/ CommandPalette
activity/ ActivityFeed
stores/ Svelte 5 reactive stores
workspace.svelte.ts Workspace state
collections.svelte.ts Collection + item state
ui.svelte.ts Sidebar, mobile state
types/index.ts TypeScript types and constants
app.css Global styles and design tokens