Paul Trowbridge
0049a391c0
There was no way to express "these segments together are the forecast". pf_iter cannot say it: it answers whether operations may write to a row, and Open Orders is loaded as reference precisely so nothing adjusts it while still being part of the forecast number. The two questions are independent, so one cannot be derived from the other. pf.log.bucket is the second axis. Free text with suggestions -- Forecast, Prior Year, Prior Prior Year, Plan -- rather than an enum, so another banner needs no migration. Blank by default, falling back in the pivot to the segment's own name, so nothing changes until something is labelled. /data and /agg emit it as pf_bucket beside pf_segment, through the pf.log join that is already there. Set it per segment in the Baseline list, which is where loads live now that the change log only shows adjustments. Needs 01_schema.sql for the column and Generate SQL for /agg to select it. 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.