pf_app
Paul Trowbridge
cdb40e7368
The panel's preview calls buildPayload itself, and the scope arrived as a parameter that the preview had no way to supply -- so it defaulted to empty and printed a payload with no scope for a write that had one. A preview that disagrees with what is sent is worse than no preview: it is the one place someone looks to check before committing a change. buildPayload reads the scope from the ref instead, so there is one payload and both callers get it. 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 | ||