[Feature Request]: MultiCombobox with loading prop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 285
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 59
Description
Feature Request Description
The current Combobox component includes a loading prop, which enables a loading indicator to signal a loading state. However, the MultiCombobox does not provide a similar API, resulting in inconsistent handling of the loading state across components. For improved developer experience and API consistency, the MultiCombobox should support the same loading prop.
Proposed Solution
- Add a
loadingprop to theMultiComboboxcomponent, mirroring the behavior and API of theCombobox's loading state. - Optionally, introduce a
delayprop to control theBusyIndicatorbehavior, allowing for customizable delay times before showing the loading indicator. - Expand support for the loading prop to the
SelectandMultiSelectcomponents to ensure consistent loading state handling across all similar components in the library.
Proposed Alternatives
If aligning the API across components is not feasible or desired, consider removing the loading prop from the Combobox component to maintain consistency and avoid API discrepancies (with 3.0.0).
Organization
No response
Additional Context
No response
Priority
Low
Privacy Policy
- I’m not disclosing any internal or sensitive information.
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 comparing the existing Combobox loading API and behavior with MultiCombobox, then review how BusyIndicator delay is handled. Confirm whether the scope includes Select and MultiSelect, or only MultiCombobox, and define done as consistent loading support and documented behavior across the agreed components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100