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> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| vendor | ||
| .gitignore | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
React + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.