Given an EuiComboBox with singleSelection={{ asPlainText: true }} and onCreateOption (see EUI docs example)
I want to be able to edit the existing selected value rather than entirely deleting it (afterall, we have the isClearable prop)
(In other words, I want the combobox to behave as a regular input field rather than as pills)
So that I can make minor adjustments without having to remember what I previously entered
This is useful for large datasets with minor variations between options.
I had considered EuiSuggest but there were no examples of enabling custom options or its use with basic options i.e. plaintext (I have over 3500 options in this dropdown, soon to be an order of magnitude or two more).
Tbh EuiCombobox and EuiSuggest are pretty similar, it'd be nice to have a Do and Don't doc for when to use each altho I see a couple issues around this already #2708 #2841
While I'm here, it'd probably be worth you adding a notice to Case-sensitive matching and Async to explain that the consumer's own onSearchChange will have to implement the case-sensitivity i.e. that they're incompatible
Given an
EuiComboBoxwithsingleSelection={{ asPlainText: true }}andonCreateOption(see EUI docs example)I want to be able to edit the existing selected value rather than entirely deleting it (afterall, we have the
isClearableprop)(In other words, I want the combobox to behave as a regular input field rather than as pills)
So that I can make minor adjustments without having to remember what I previously entered
This is useful for large datasets with minor variations between options.
I had considered
EuiSuggestbut there were no examples of enabling custom options or its use with basic options i.e. plaintext (I have over 3500 options in this dropdown, soon to be an order of magnitude or two more).Tbh EuiCombobox and EuiSuggest are pretty similar, it'd be nice to have a Do and Don't doc for when to use each altho I see a couple issues around this already #2708 #2841
While I'm here, it'd probably be worth you adding a notice to Case-sensitive matching and Async to explain that the consumer's own
onSearchChangewill have to implement the case-sensitivity i.e. that they're incompatible