Dropdown componentsearchInput so that it provides a custom onChange callback.Typing inside of Dropdown.SearchInput should only trigger its onChange.
Typing triggers input's onChange first and then dropdown's onChange callbacks.
0.82.3
馃憢 Thanks for opening your first issue here! If you're reporting a 馃悶 bug, please make sure you've completed all the fields in the issue template so we can best help.
We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Thanks, awesome report! PR is coming.
Amazing work! You guys rock :guitar:
Fixed in #3123, will come with the next release.
Just a question, you have overrided onSearchChange in your test, whereas I mentioned that it's
onChange that causes the problem. Is that correct?
wrapperShallow(
<Dropdown
onSearchChange={onSearchChange}
options={options}
search
searchInput={{ onChange: onInputChange }}
/>,
)
Yes, it's a correct change.
<Dropdown
searchInput={{ onChange: (e, { value }) => console.log('input onChange: ' + value) }}
onChange={(e, { value }) => console.log('dropdown onChange:' + value)}
onSearchChange={(e, { searchQuery }) => console.log('dropdown onSearchChange: ' + searchQuery)}
options={[
{ text: 'text1', value: '1' },
{ text: 'text2', value: '2' },
]}
closeOnChange
search
multiple
selection
/>
See result:

onChange will be called only when a value will be selected.
The same code on master:

Most helpful comment
Thanks, awesome report! PR is coming.