Selva

@robertino-iorii you can use `onSearchInputChange` to listen for search text changes & fetch the results via api & provide them as `options`

Ahh! just noticed that `onSearchInputChange` works with `TypeAhead` & `PowerSelectMultiple` components but does not work with `PowerSelect` 🐛 🐛 🐛

Forgot to update here, the issue with `PowerSelect` is fixed btw

@nypinstripes Appreciate your nice words. I'd go ahead with running the codemod to resolve the deprecation notices as a short term fix I've plans to rewrite this package to use...

~Seems like we need to add `optionValuePath` option even in this approach~ ~*Updated the code in the issue description ^^*~

Is this a normal behavior in selects ? Can you cite some examples that have this behavior ? Also, the `disabled` should be respected. Meaning, when the powerselect is disabled,...

We have `showClear` to show the close icon on the rhs of the powerselect. Setting it to `false` will allow to you change the value but you can't clear them....

However, you can achieve the same functionality by composing the component & handling the keyDown event. I'd prefer to wait for more feedbacks on this feature

@Suvra1990 published 1.0.0-beta.15 🎉

@SCasarotto Do you think this addon helps ?https://github.com/storybooks/storybook/blob/next/addons/storysource/README.md