bucket_order fed the ordering expressions and nothing else, so its up/down list is gone. The datalist it shared state with stays, now offering the buckets actually in use plus the four conventional names carried with their prefixes -- a near-miss spelling silently splits a column in two, so the options are worth more than they were. saveBucket was a duplicate of saveLogField left behind by af9e6de's refactor; the bucket cell goes through saveLogField like the label does. Both confirmations now say to reload the Forecast view, which is true of a label for the same reason it was true of a bucket: it is part of the aggregated row. pf.log.seq and pf.version.bucket_order are no longer read anywhere. The columns stay -- dropping them is not worth the migration, and nothing costs anything by their being there. 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.