Autofill stopped filling anything as soon as the member endpoint answered, because a hit was treated as the only possible answer: if the key was not in the list, it returned rather than trying the source. An empty list counted as an answer too, which is the state while a refresh is still running -- so wiring up master data broke the behaviour it was meant to improve, for everyone who had not finished building the list yet. A miss is not an answer. Empty list, or a key the list does not know, both fall through to the source lookup as before. It costs one request, on a path that only runs when someone types a value. 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.