Paul Trowbridge
c6ef350283
A slice carries every value as a string -- built from filters the grid reports, and shaped to survive JSON on the way to the API. Perspective matches on type, and a string '2027' against an integer column is not a filter that matches nothing, it is a filter that is dropped. So the pivot's own season filter never reached the ledger: with the grid scoped to sseas_e = 2027 the ledger totalled 956,485.13 against a cell reading 921,225.71, the difference being eleven rows of a baseline segment whose shipments fall in the next season. Only dates were being coerced, and only because someone had hit this before with them. Values are now typed against the loaded table's schema rather than against col_meta's role, which is the thing that actually decides the match. The server side was already right -- Postgres casts the literal -- and returns 921,225.71 for the same slice. Co-Authored-By: Claude Opus 5 (1M context) <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.