-
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
If options are being returned by a call or async but all options are returned when the call returns. #1250
Comments
I thought if there was a select component like async, creatable which would handle this case and send options to select |
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 limited efforts to maintain the latest version. If you feel this issue / pull request 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. |
Consider the case where I have a component called my-comp which is rendering a reat-select and I need to load the options from some call or promise. A general thing to do in this case is to make the call during my-comp' constructor, componentDidMount and when I get the options I again render my component this time providing react-select with the fetched options.
But now applications don't want many of there components having state(I am not sure about that, I just like dat).
One hack I found for this is using react select-Asyc and sending options on the first call and ignoring the rest and sending the options I fetched the first time. But in this case for each input rather then just filtering options react select will think of new options and set in its state which seems like a hack.
So is there a some solution already in react-select that I am not able to figure out or something could be done about this?
The text was updated successfully, but these errors were encountered: