pf_app/routes
Paul Trowbridge 15ab5a3a13 Tag operation result rows with pf_note and pf_op
Forecast tables don't carry pf_note; it's joined from pf.log on /data
fetch. RETURNING * from scale/recode/clone INSERTs lacks those fields,
so rows appended via table.update arrived with pf_note null until a
reload re-ran the join. Inject pf_note and pf_op server-side from the
request before responding.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-28 21:33:32 -04:00
..
log.js Undo deletes rows in place instead of reloading the forecast 2026-04-28 20:21:13 -04:00
operations.js Tag operation result rows with pf_note and pf_op 2026-04-28 21:33:32 -04:00
sources.js Scaffold React/Vite/Tailwind UI with 3-step Setup → Baseline → Forecast flow 2026-04-25 16:28:45 -04:00
tables.js Expose pf_note/pf_op in forecast data; fix tables list duplicates 2026-04-28 19:51:45 -04:00
versions.js Refactor sources UI, rename pf_ system cols, replace filter builder with raw SQL 2026-04-03 00:47:57 -04:00