Paul Trowbridge
91c53ac6d8
App.jsx fell back to versions[0] when localStorage held no selection, and the version list is ordered created_at DESC -- so a fresh browser landed on whatever version was created last. That is a scratch scenario as readily as the plan, and sales accounts, which never pick a version themselves, had no way back to the one they were meant to read. pf.version.is_default names the landing version, at most one per source by partial unique index, the way pf.layout.is_default already works. Setting it is admin-only and enforced in the route: it decides where everyone else lands, so it follows the pf.log rule rather than being the version's own setting like its name. A stored selection still wins -- the default is the fallback, not an override, so nobody building scenarios is thrown back to the plan on every load. 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.