Components to create

[jamesplease]

To Create

Regular

• List ( List #174 )
• AppHeader ( Create Navbar component #16, App Bar #239 )
• AppPicker
• DatePicker Add DatePicker Component #31 (less important)

React Over/Popper

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

Nvm

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

Created

• Button
• Checkbox (see Checkbox: switch to circles for animation #4 )
• Switch
• Avatar
• Icons
• Spinner
• Radio button
• Dialog ( Rewrite modal #3 )
• Elevation
• Chip, three kinds ( see: Chip color: grey by default #42, "Selected" state for chips #34 )
• Menu
• Snackbar
• InputChip
• Table
• Inline spinner
• Input
• IconButton
• Field
• Expandable
• ExpansionPanel ( Expansion Panel #173 )
• TextArea
• ProgressBar (see ProgressBar #206)
• Navigation (see Navigation updates #53 / this )

---

Possible:

• More managed dropdowns? Multiselect? (see Bulk delete for dropdown #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