pf_app
Paul Trowbridge
2306315a17
PUT /versions/:id/baseline/:logid deletes the log row and inserts a fresh one from the stored template, so every field the form does not send comes back null. That took the label and the bucket with it, and the tag besides -- the segment form has no tag input at all, so a tag could not survive an edit made for any other reason. The route now hands back what it was not given, reading the row it is about to replace. `??` rather than `||`: an empty string is the form clearing a field deliberately, undefined is the form not carrying it. The load templates gained a tag token to receive it. Stored templates are per-source and were generated before any of this existed, which is the other half of why labels vanished -- source 14's had no label column to write to. Regenerated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||