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>
45 lines
1.4 KiB
Text
45 lines
1.4 KiB
Text
tossme/
|
|
examples/
|
|
.env
|
|
.vscode
|
|
|
|
# Per-project Claude Code state (planning files, agent transcripts, etc.)
|
|
.claude/
|
|
|
|
# Session planning (never public)
|
|
PLAN.md
|
|
|
|
# Node dependencies
|
|
node_modules/
|
|
|
|
# Test report and results
|
|
playwright-report/
|
|
test-results/
|
|
|
|
# Build artifacts. dist/ is ignored everywhere: per-tool dist/<tool>.html
|
|
# is a transient build output (and the canonical thing tests open via
|
|
# file://), and dist/release-output/ is the local-only release bundle
|
|
# produced by `./build alpha|beta|release`, then rsync'd to the live
|
|
# site by `./deploy`. Nothing in dist/ should be committed.
|
|
#
|
|
# Hand-edited website content (index.html, reference.html, css/, js/,
|
|
# img/) lives in a SEPARATE Codeberg repo at codeberg.org/VARASYS/
|
|
# ZDDC-website, typically cloned at ~/src/zddc-website/. Release
|
|
# artifacts are NOT in git history at all — they're produced by this
|
|
# repo's build, rsync'd to /srv/zddc/releases/ on the deploy host,
|
|
# and reproducible from any <tool>-vX.Y.Z tag.
|
|
dist/
|
|
|
|
# Locally-compiled zddc-server binary. `(cd zddc && go build ./cmd/zddc-server)`
|
|
# drops the binary at zddc/zddc-server; the canonical released artifacts live
|
|
# under dist/release-output/zddc-server_* with platform suffixes and signing.
|
|
zddc/zddc-server
|
|
zddc/zddc-server.exe
|
|
|
|
# IDE and project files
|
|
.opencode/
|
|
opencode.json
|
|
package-lock.json
|
|
zddc-knowledge*.json
|
|
zddc-knowledge*.md
|
|
zddc-knowledge*.html
|