-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to control isLoading and the spinner? #405
Comments
In docs on http://jedwatson.github.io/react-select/ you should see the spinner when typing 'a' in the last box. And you should also see it in your own examples, after the your function from |
I agree with @hipertracker. The spinner is not automatically shown when the component is loading the data for the very first time, i.e. when I've had a look through the source, and I believe that the method Something like: autoloadAsyncOptions: function() {
this.setState({
isLoading: true
});
this.loadAsyncOptions((this.props.value || ''), { isLoading: false }, () => {
// update with fetched but don't focus
this.setValue(this.props.value, false);
});
}, |
I actually have the opposite problem, my loading circle never goes away even after I've selected options. Is this related? |
@sslotsky the same shit |
Related to this: although the official documentation says that you can pass an
This is not true. The prop is never read/used by the Async component |
Hello - In an effort to sustain the We understand this might be inconvenient but in the best interest of supporting the broader community we have to direct our efforts towards the current major version. If you aren't using the latest version of However, if you feel this issue is still relevant and you'd like us to review it - please leave a comment and we'll do our best to get back to you! |
Is there any example which for asynOptions which could display spinner showing up during waiting for the data? I can load options from the server but the field is not showing any spinner. Just no options, until they are available. The original example from README file is too simple.
The text was updated successfully, but these errors were encountered: