With the prefix stored in pf.log.label there is nothing left to compute, so all of it goes: ORDER_EXPR_NAMES, buildOrderExpression and its ExprTK printable-ASCII-per-byte guard, SYNTHETIC_SEGMENTS and its 98/99 ordinals, syncOrderExpressions with its two self-issued fetches, the dbgOrder tracing, and the three places it had to be re-applied because restore() replaces `expressions` wholesale. What remains is a list of the names it used to manage, stripped by cleanLayout so a layout saved under the old scheme does not keep ordering by a rule nothing updates. The strip goes before the axis filter: dropping them from `expressions` is what makes the existing ok() reject them on every axis, which restore() requires -- an expression the pivot is using cannot vanish from underneath it. Net 250 lines out. The Baseline page's reorder buttons no longer feed anything and go next. 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.