Paul Trowbridge
ad02aba8fb
Baseline and reference loads are segment construction, not forecasting. Listing them beside the adjustments buries what the log is actually for -- on version 29 that is four load entries against however many adjustments -- and offers an undo next to them that would silently gut the version. They are managed in the Baseline view instead, which is where they can be edited in place and their date ranges seen. Filtered in the dialog rather than in the route, since Baseline.jsx and the ledger's tag lookup both read the same endpoint and do want every entry. 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.