pf_app
Paul Trowbridge
1d2fc97eee
Three things about the change log, from using it. The slice column grew to a block per entry once it listed lines, which is too much for a table you scan. It is one truncated line now: a single slice reads as its fields, and a dragged region as "5 slices · omon = 07 - Dec … 11 - Apr" -- enough to recognise the entry. There was no indication of what an entry did to the numbers, which is the first thing you want from a change log. The route already returned value_total and it simply was not rendered. Added, signed and coloured, so a list of adjustments reads as a list of impacts. And clicking a row now opens slice and params as formatted JSON -- the exact payload that went over the route, including the increments and the plug, which no amount of summarising in the cell was going to convey. 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 | ||