Multi Select Menu

[kumarGayu]

cc: @asangma @patrickarlt
I can start looking at development based existing design. may be we can enhance when we have better design.

This is required for chart authoring experience and designed by Mike Stinson.

[babakbolour]

you are all aware of the pluralization issue with this, right? best way to implement this is:
"Fields selected: 3"

[macandcheese]

This is similar to filter dropdown (https://github.com/ArcGIS/calcite-components/projects/2#card-22328663, http://esri.github.io/calcite-web/documentation/patterns/#filter-dropdown), which is in Wishlist for now because I think there are a ton of variants across apps of "something like this" that should share underlying components... input fields, chips (https://material.io/design/components/chips.html), dropdowns, etc.,

I think it's all part of a story that needs more design consideration to make sure all possible variants look the same - simple multi-select like this, typeahead from an input multi-select, etc.

[asangma]

Can this include search? 👁 👁

[macandcheese]

I'd imagine we would want to replicate "filtering" a pre-determined list like we do here: http://esri.github.io/calcite-web/documentation/patterns/#filter-dropdown

For search, hopefully it could be extended by the consumer to look the same to an end user, but we probably don't want to handle any backend searches. Maybe "app-components" could contain more advanced functionality while sharing styles and appearance.

I will make an issue for filter chips that could support icon, "close", etc., since that seems like a re-usable component for a few larger patterns.

[asangma]

@macandcheese Yo...sorry for the communication gap.
And yeah, I meant more client-side filtering than search.
For the purposes of browsing a list and selecting one/many items to populate an input for a configuration panel, the text filtering should be enough.

[patrickarlt]

Closing to track in #61.