ZDDC
9ca36f25d8
Tables is the eighth HTML tool: a read-only tabular view over a
directory of YAML files declared via `tables:` in `.zddc`. Anchor use
case is the Master Deliverables List, where each row is one
`<tracking>.yaml` under `Archive/<Party>/MDL/`. Rows click through to
the existing form renderer for editing.
Schema (zddc/internal/zddc/file.go)
- New `Tables map[string]string` on ZddcFile. Map key becomes the URL
stem (`tables[MDL]` → `<dir>/MDL.table.html`); the value is a path
relative to the .zddc pointing at a `*.table.yaml` spec describing
columns + the rows directory. No upward cascade in v1 — each
directory hosting a table declares it directly.
Server handler (zddc/internal/handler/tablehandler.go)
- `RecognizeTableRequest` matches GET `/<dir>/<name>.table.html`
against the cascade's `tables:` declarations. Dispatch routes
table requests before the form-system intercept.
- `ServeTable` ACL-gates with `policy.ActionRead` and serves the
embedded `tables.html` template; client walks the directory itself
via the listing JSON or FS Access API.
- tables.html embedded via //go:embed — same pattern as form.html.
Frontend (tables/)
- Vanilla JS: app/context/util/filters/sort/render/main modules.
- Reads spec + row YAML files via window.zddc.source (HTTP polyfill
or local FS handle); js-yaml 4.1.0 vendored in shared/vendor for
client-side parsing.
- Sample fixtures under tables/sample/ for local testing.
Build + CI
- Lockstep build registers tables alongside the other 7 tools (HTML
output, embed mirror, versions.txt, release-output, tags).
- Playwright project added; `npx playwright test --project=tables`
is part of `npm test`.
Drive-by: rename mdedit Playwright selectors `#select-directory` →
`#addDirectoryBtn` to fix three pre-existing failing tests.
Drive-by: ignore locally-built `zddc/zddc-server` binary so it doesn't
get accidentally staged.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
39 lines
1 KiB
YAML
39 lines
1 KiB
YAML
# Row schema for one Master Deliverables List entry. The table tool
|
|
# uses this as both the column-type source (formats / enums) and the
|
|
# "click-row → edit" form spec. The form handler also serves it
|
|
# directly as MDL.form.html for adding new entries.
|
|
|
|
title: Deliverable
|
|
description: One expected deliverable, tracked across parties.
|
|
|
|
schema:
|
|
type: object
|
|
required: [id, title, party, dueDate, status]
|
|
additionalProperties: false
|
|
properties:
|
|
id:
|
|
type: string
|
|
title: ID
|
|
description: Tracking identifier (e.g. D-001).
|
|
minLength: 1
|
|
title:
|
|
type: string
|
|
title: Deliverable
|
|
description: Short description of what is to be delivered.
|
|
minLength: 1
|
|
party:
|
|
type: string
|
|
title: Party
|
|
enum: [Acme, Beta, Gamma]
|
|
dueDate:
|
|
type: string
|
|
format: date
|
|
title: Due date
|
|
status:
|
|
type: string
|
|
title: Status
|
|
enum: [pending, submitted, accepted, rejected]
|
|
notes:
|
|
type: string
|
|
title: Notes
|
|
description: Free-text notes (optional).
|