You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to review some implementation changes to SingleSelect that alters both how consumers work with the component.
SingleSelect should focus on being a text input way of filtering a list of options. A dropdown or select without a text input should belong to a different component.
SingleSelect should be more opinionated about how to render a set of options, potentially deferring to the consumer to produce the DOM for the individual options, but producing a wrapper and potentially default implementation of the render.
I think the relationship between menu and list is confusing and makes reasoning about the performance harder.
The text was updated successfully, but these errors were encountered:
I would like to review some implementation changes to SingleSelect that alters both how consumers work with the component.
SingleSelect should focus on being a text input way of filtering a list of options. A dropdown or select without a text input should belong to a different component.
SingleSelect should be more opinionated about how to render a set of options, potentially deferring to the consumer to produce the DOM for the individual options, but producing a wrapper and potentially default implementation of the render.
I think the relationship between menu and list is confusing and makes reasoning about the performance harder.
The text was updated successfully, but these errors were encountered: