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> |
||
|---|---|---|
| .. | ||
| assets | ||
| components | ||
| views | ||
| App.css | ||
| App.jsx | ||
| auth.jsx | ||
| index.css | ||
| main.jsx | ||
| theme.jsx | ||