pf_app
Paul Trowbridge
bc5ce496b7
BridgeView mounts once, up front, before anything has ever been selected on the pivot -- so its scope defaulted to "Pivot's filters" (effectively the whole version) regardless of a selection made afterward. Scope now tracks the live selection until the user picks a scope button themselves. Even when scope was "Selection", the filter it built dropped pf_segment/pf_bucket-keyed slice entries entirely and matched a blank dimension value with `== null`, which this engine treats as a dropped predicate rather than IS NULL -- both widen the bridged rows past what was actually selected, the same failure mode the ledger's totalsFor in Forecast.jsx was hardened against. Bridge's selection filter now mirrors that logic. Co-Authored-By: Claude Sonnet 5 <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 | ||