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>
41 lines
1.1 KiB
YAML
41 lines
1.1 KiB
YAML
# Master Deliverables List — table spec.
|
|
#
|
|
# Columns are an explicit ordered subset of the row schema. The renderer
|
|
# does not auto-derive columns from the schema. `field` is either a
|
|
# top-level key on the row YAML or a JSON Pointer (RFC 6901) for nested
|
|
# values.
|
|
|
|
title: Master Deliverables List
|
|
description: Sample MDL spec used for development and tests.
|
|
|
|
# Path to the form spec that defines each row's JSON schema. Click-row
|
|
# in the table opens this form for the picked row. The form spec must be
|
|
# named <name>.form.yaml where <name> matches both the rows directory
|
|
# basename and the .zddc declaration key (here: MDL).
|
|
rowSchema: ./MDL.form.yaml
|
|
|
|
# Directory of *.yaml row files, relative to this spec. Non-recursive.
|
|
rows: ./MDL
|
|
|
|
columns:
|
|
- field: id
|
|
title: ID
|
|
width: 7em
|
|
sort: asc
|
|
- field: title
|
|
title: Deliverable
|
|
- field: party
|
|
title: Party
|
|
enum: [Acme, Beta, Gamma]
|
|
- field: dueDate
|
|
title: Due
|
|
format: date
|
|
- field: status
|
|
title: Status
|
|
enum: [pending, submitted, accepted, rejected]
|
|
|
|
defaults:
|
|
sort:
|
|
- { field: dueDate, dir: asc }
|
|
filter:
|
|
status: [pending, submitted]
|