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
UX has requested that the Combobox provide a filter option that would match the user input value to any part of the text in the dropdown option text.
The primary use-case for this feature would be matching a common term for a subset of options that doesn't appear at the front of the text.
💁 Proposed Solution
The FAST Select offers a set of "autocomplete" options that include inline (which autocompletes from the beginning), 'list' (which just filters matching items from the beginning), 'both' (which both filters and autocompletes), and 'none'.
We can't really extend this solution since it's a closed type that specifies the options to select from. Even if we could extend it, it would be awkward, because what would 'both' mean with this new filter option? The options available to us to support this feature seem to be the following:
Push FAST to introduce this feature in the way they think is best. I've started the Discord discussion here.
Add the new filter option to nimble-combobox. While technically this would be implementation-light, it would also make for an ugly implementation if we had to have logic that had to handle the insane case where both the new option we provided as set as well as the FAST option.
Fork the fast-foundationCombobox and provide the API/implementation we desire. This has the obvious drawback of us being severed from any improvements/bug fixes made to the FAST Combobox.
Other?
The text was updated successfully, but these errors were encountered:
😯 Problem to Solve
UX has requested that the
Combobox
provide a filter option that would match the user input value to any part of the text in the dropdown option text.The primary use-case for this feature would be matching a common term for a subset of options that doesn't appear at the front of the text.
💁 Proposed Solution
The FAST
Select
offers a set of "autocomplete" options that includeinline
(which autocompletes from the beginning), 'list' (which just filters matching items from the beginning), 'both' (which both filters and autocompletes), and 'none'.We can't really extend this solution since it's a closed type that specifies the options to select from. Even if we could extend it, it would be awkward, because what would 'both' mean with this new filter option? The options available to us to support this feature seem to be the following:
nimble-combobox
. While technically this would be implementation-light, it would also make for an ugly implementation if we had to have logic that had to handle the insane case where both the new option we provided as set as well as the FAST option.fast-foundation
Combobox
and provide the API/implementation we desire. This has the obvious drawback of us being severed from any improvements/bug fixes made to the FASTCombobox
.The text was updated successfully, but these errors were encountered: