-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Description
Problem
We need to settle on the API for how to specify Dropdown (aka ComboBox)'s items. This requires some prototyping to figure out what implementation is feasible and fits in with our component architecture.
Appetite
3 weeks
Solution
Writing the spec requires some background work first:
- Finalize name of "Dropdown" vs. "ComboBox". It's currently planned as "Dropdown", but that may have been assuming that there would be a separate "ComboBox" component.
- Prototype specifying items and groups as children of the
<ComboBox>component, rather than an array in a slot. The primary concern is having the root ComboBox able to keep track of the ordered list of items (possibly inside groups, and possibly virtualized). - Prototype how to structure it so that there is no dependency on
Inputif the combo box is not editable. - Background research about other component libraries' ComboBox/Dropdown
Risks (Rabbit holes)
The draft implementation could easily get too detailed/complete before the approach has been reviewed by the team. It will be necessary to keep the implementation rough and focus on the main open questions rather than getting it fully functional and pretty.
Out of scope (No-gos)
This does not include actually writing a working, styled implementation of ComboBox/Dropdown.
Reactions are currently unavailable