max-mapper / max-mapper/flavors
text filtering is slow
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
i'm brute force mapping over all entries when the filter input changes
it would be nice to either put this in a web worker so it doesnt block the UI or use some faster text filtering data structure + algorithm
Contributor guide
No contributing guide indexed for this repository
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 tracing the filter input change handler and the brute-force mapping over all entries. Compare the web-worker and faster text-filtering data-structure approaches using representative flavor data. Done means filtering no longer blocks the UI while returning the expected matching entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100