Paul Trowbridge
318a09b6f2
A slice as broad as a whole bucket reached every entry on the version, and the walk stopped being a walk -- roughly 44 lines on the version this was built against, where there are about a dozen things to say. Three causes, three fixes. Untagged adjustments had a line each, labelled "Scale #226" -- a row spent to say nothing, 28 of them. They collapse to one line that counts them. Tags grouped by exact text, so "Keystone reduction" and "Keystone Reduction" reported as two initiatives, as did four spellings of moved to a different sku. Grouping is case-insensitive now and the line shows whichever spelling was used most. The tags themselves are untouched; wording variants are still separate lines, and that is for whoever typed them. What is left is capped: the loads stay whole, since they are the shape of the forecast, and the adjustments keep the six largest with the rest rolled into one line carrying its own subtotal. Still arithmetically the walk -- addition does not care about the order -- and the rollup expands. 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.