Components to create

[jamesplease]

To Create

Regular

• [ ] List ( #174 )
• [ ] AppHeader ( #16, #239 )
• [ ] AppPicker
• [ ] DatePicker #31 (less important)

React Over/Popper

• [ ] Popover (elevation, arrow. used by Menus and possibly others)
• [ ] Controlled Dropdown
• [ ] Managed "simple" Select ( #33, #35 )
• [ ] Managed "async" autocomplete ( #33, #35 )
• [ ] Managed sync autocomplete ( #33, #35 )
• [ ] Tooltip (wait for React Over?)

Nvm

• ButtonGroup Chips can accomplish this now
• Tag Chips can be tags now

Created

• [x] Button
• [x] Checkbox (see #4 )
• [x] Switch
• [x] Avatar
• [x] Icons
• [x] Spinner
• [x] Radio button
• [x] Dialog ( #3 )
• [x] Elevation
• [x] Chip, three kinds ( see: #42, #34 )
• [x] Menu
• [x] Snackbar
• [x] InputChip
• [x] Table
• [x] Inline spinner
• [x] Input
• [x] IconButton
• [x] Field
• [x] Expandable
• [x] ExpansionPanel ( #173 )
• [x] TextArea
• [x] ProgressBar (see #206)
• [x] Navigation (see #53 / this )

---

Possible:

• More managed dropdowns? Multiselect? (see #35 )

[conorhastings]

how do you envision the async autocomplete, consuming a promise and filtering from response?

This one requires a lot of though imo:

• caching
• loading state
• debouncing or throttling
• probably other things

[jamesplease]

To be completely honest, I haven't put any thought into what that component will look like yet. We plan to build a "basic" dropdown first, to keep the problem space narrow, and then branch out from there.

[conorhastings]

yeah thinks that's the right way to go, something you really want to get right, and with the primitives, async is implementable in userland