PUT /versions/:id has taken name and description since it existed; only the fallback-name fields ever called it, so the one thing a version's name could not be was changed. A This forecast panel on the Baseline page now saves both on blur. Safe at any time, closed versions included: nothing derives from the name. The forecast table is keyed on the id, as are pf.log, pf.layout and the UI's localStorage. Two edges the route left open. (source_id, name) is unique, so a rename can collide -- it now answers 409 with the same sentence the POST has always used, rather than a raw Postgres message that reads as a server fault. And the UPDATE COALESCEs a falsy name back to the existing one, so a blank box would have looked saved and changed nothing; that is refused where it is typed. 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.