The ledger filtered on every column of the loaded table, while the request kept only pf_segment and pf_bucket and stripped pf_iter, pf_note, pf_op, pf_user and pf_logid. Under the default layout, grouped by pf_iter, a click on a customer's `scale` row totalled the scale rows and wrote to every row the customer has -- on GRIFFIN, $4.5M shown against $9.7M written. They now travel: pf_iter / pf_user / pf_logid compared directly, pf_note / pf_op resolved to log ids as pf_segment / pf_bucket are, a null note as IS NULL. They narrow a slice but do not make one selective on their own. Each scale also carries `expected`, the Result line as a change, and `plug`, both kept in the log's params beside `resolved` so a panel/server disagreement can be found by reading it. Nothing compares them yet. Co-Authored-By: Claude Opus 5.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.