Paul Trowbridge
1d2fc97eee
Three things about the change log, from using it. The slice column grew to a block per entry once it listed lines, which is too much for a table you scan. It is one truncated line now: a single slice reads as its fields, and a dragged region as "5 slices · omon = 07 - Dec … 11 - Apr" -- enough to recognise the entry. There was no indication of what an entry did to the numbers, which is the first thing you want from a change log. The route already returned value_total and it simply was not rendered. Added, signed and coloured, so a list of adjustments reads as a list of impacts. And clicking a row now opens slice and params as formatted JSON -- the exact payload that went over the route, including the increments and the plug, which no amount of summarising in the cell was going to convey. 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.