Paul Trowbridge
8aa0ae2ece
Two causes, both mine, both triggered by adjusting the layout. A zero size was being treated as the viewer going away, and opening Perspective's settings sidebar collapses the datagrid for a frame. The return then re-applied the stored row depth over whatever had been expanded by hand. Only lost intersection counts as a departure now; a zero size is a transient of layout, not an absence. And perspective-config-update fires for anything in the config, the settings flag included -- not only for split_by. While collapsed the live split_by is a truncation of the full hierarchy, so adopting it recorded the truncation as the hierarchy and put the deeper levels out of reach. A genuine rearrangement is not a prefix of what we already hold, which is the difference the handler now tests. 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.