Paul Trowbridge
99d7fe72d8
A tag was only ever a value typed on a pf.log entry, so the only way to change one was to find every entry carrying it in the change log and edit each. Nothing showed what the list was, and the bridge groups on this column -- so "Pull Forward" and "Pulled Forward" read as two initiatives with no way to make them one. PATCH /versions/:id/tags rewrites every entry carrying `from`. A `to` that already exists merges the two, an empty one clears the tag; the panel confirms both, since neither is visible as a diff afterwards. Permission is the pf.log rule applied to every entry the tag is on rather than most of them: a half-applied rename leaves the initiative split, which is what the rename was for. GET /versions/:id/tags now returns owners and can_edit so the panel can grey the row out instead of offering a click that answers 403. On the Baseline page, next to the other version-level settings -- the Forecast page edits one entry's tag, this edits the column. 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.