Async Select currently does not interact with defaultValue and defaultInputValue correctly

[gwyneplaine]

This is because unlike <Creatable/> and the base <Select/> component, we do not wrap AsyncSelect in the StateManager, and in fact wrap the state managed Select in the makeAsyncSelect method.

The defaultValue and defaultInputValue props are still interacting as expected with the wrapped base select, however they are not currently interacting as expected with the wrapping async component.

See an example of this in CodeSandbox.

CC: @JedWatson @jossmac

[lucasbesen]

@JedWatson @gwyneplaine news here?

[guilhermedecampo]

interesting situation

[ebonow]

@gwyneplaine would you mind taking another look at this? It appears that the defaultValue is showing up as expected in the example you provided.

I am also not able to replicate when testing defaultInputValue

https://codesandbox.io/s/beautiful-kepler-ulfzx?file=/src/App.js

[gwyneplaine]

Thanks for this @ebonow , I don’t remember what the issue in regards to defaultValue was if i’m honest.
However i believe the expectation here is that the defaultInputValue would filter down the set of options in loadOptions on mount

(this is better illustrated with the following sandbox)
https://codesandbox.io/s/affectionate-engelbart-5y6my?file=/src/App.js

The expectation here is that because defaultOption is being specified, according to our code loadOptions should be called. But in this case its called with an empty inputValue rather than the defaultInputValue provided as props to the AsyncSelect

[ebonow]

Interesting. Def worth a conversation as my understanding was that loadOptions was only called on key press rather than changes in inputValue. I have seen other issues or bug requests when users pass in a change in inputValue controlled from another input. I'd be open for anything that makes calling the loadOptions function easier to call