Paul Trowbridge
b65da53360
Recoding to a part meant typing a code from memory into a plain text box, with the only feedback being that the sibling autofill either fired or silently did nothing. The values endpoint already existed but returned every distinct value with no filter and no limit, which for part on osm_skinny is 11,290 rows -- too slow to open and no easier to read than a short list. It now takes ?q= and ?limit=, so the field fetches matches for what has been typed so far, debounced 200ms, and offers them through a native datalist. Only key columns get it, which is the same condition the endpoint already enforced, and the same one that decides whether the dim_group sibling lookup runs on blur. So on osm_skinny it is part and customer: type 1601 and the eight parts containing it are offered; pick one and the nine part-group columns fill themselves. 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.