JedWatson / JedWatson/react-select
Select becomes unusable with above 20000 options
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
When react select has more than 20.000 options it is no longer usable.
Render and search takes a lot of time, so users simply close the app because of this component.
Please note, that there is a potential fix for this in PR #4515 but that was not merged.
Currently developers have to integrate other components and packages just to fix this simple issue that already has a fix.
In case possible, please have a look and merge that PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #4515 and the current Select component implementation. Reproduce rendering and search with more than 20,000 options, then compare the proposed approach with current behavior. Done means the component remains usable at that scale without requiring an alternative package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100