Paul Trowbridge
518a0ca5ba
Three changes, one feature: a period with no baseline borrows a shape from prior year or plan. The generator handled one date group. sql_generator.js used find(), so a source with order, requested and ship date groups derived the order one and copied the other two raw -- shifted dates against unshifted period labels. Every group now gets its own join, and they are LEFT rather than inner: an order that has not shipped has no ship date, and an inner join would have dropped the row from the load entirely rather than leaving its period columns empty. dateGroupsOf() is now shared, like grainOf, so the routes and the generator agree on membership and on join aliases. Clone carries every date column rather than only the primary one, since it is the operation that moves rows through time, and re-derives the period dimensions from pf.dim_period against the shifted date instead of copying them from the row being cloned. from_logid names the segment to copy from, replacing the exclude clause for that one entry rather than widening it. Rows written stay pf_iter = 'clone', so scale applies to them afterwards as a second step. set is no longer required: copying a segment forward unchanged is a reasonable thing to ask for. Needs dim_period_col set in Setup (fisc_year on oseas/rseas/sseas_e, fisc_month_abbr on omon/rmon/smon_e) and Generate SQL. 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.