Wording variants are a user problem, but the completion was making it one: a native datalist substring-matches, so typing "moved to different sku" never offered "moved to a different sku" -- one inserted word and the existing tag is invisible. Four spellings of that initiative are on the current version, with a ledger line each. TagInput matches on words instead. Both sides lowercased, stripped of punctuation, relieved of stopwords and lightly stemmed, so Pulled Forward finds Pull Forward. Typing something that reduces to an existing tag without being it says so: already used as X, use that. Nothing is merged automatically. The suggestion is offered and the typing stays yours -- moved to another sku is genuinely a different sentence from moved to a different sku, and only the person typing knows whether it is a different thing. 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.