Add a way to show a progress indicator while fetching items for combobox
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by comparing this request with issue #1311 and reviewing the existing select progress-indicator API. Then examine the combobox autocomplete modes and how they differ from select filtering. Done requires an agreed API and behavior for showing progress while fetching combobox items.
Written by the indexing model from the issue text.
Description
🙋 Feature Request
😯 Problem to Solve
This is the equivalent of #1311 but for the combobox. Some clients may need to do a network request to request combobox items based on the current text. While waiting for that request to complete they would like to show a spinner that indicates something is happening.
At this point we're not aware of specific clients that need this. We're planning to migrate many existing Nimble comboboxes and Material autocompletes to use the new select features and this might negate the need for it or might reveal that some use cases require it.
💁 Proposed Solution
The API should likely follow what we did for select, but there are complications around component differences like the fact that combobox has different autocomplete modes while the select has different search/filter modes. One idea is to remove the autocomplete modes from the combobox and align the API more closely with select filtering.
📋 Tasks
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 14
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
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.
More from ni/nimble
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
bug triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
blocked bug triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·