{"action":"opened","issue":{"url":"https://api.github.com/repos/JedWatson/react-select/issues/699","labels_url":"https://api.github.com/repos/JedWatson/react-select/issues/699/labels{/name}","comments_url":"https://api.github.com/repos/JedWatson/react-select/issues/699/comments","events_url":"https://api.github.com/repos/JedWatson/react-select/issues/699/events","html_url":"https://github.com/JedWatson/react-select/issues/699","id":125535389,"number":699,"title":"Reseting asyncOptions","user":{"login":"scruffles","id":145380,"avatar_url":"https://avatars.githubusercontent.com/u/145380?v=3","gravatar_id":"","url":"https://api.github.com/users/scruffles","html_url":"https://github.com/scruffles","followers_url":"https://api.github.com/users/scruffles/followers","following_url":"https://api.github.com/users/scruffles/following{/other_user}","gists_url":"https://api.github.com/users/scruffles/gists{/gist_id}","starred_url":"https://api.github.com/users/scruffles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scruffles/subscriptions","organizations_url":"https://api.github.com/users/scruffles/orgs","repos_url":"https://api.github.com/users/scruffles/repos","events_url":"https://api.github.com/users/scruffles/events{/privacy}","received_events_url":"https://api.github.com/users/scruffles/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-08T03:32:51Z","updated_at":"2016-01-08T03:32:51Z","closed_at":null,"body":"I'm not sure if this is a bug, or there's a way to get this behavior that I'm not finding.  I'm using react-select 1.0.0-beta8\r\n\r\nI have two select fields.  The first field changes the type (and therefore the list of options available) in the second.  If I were using 'options', I would just replace the options list in the second field when the first field changes.  I need to use asyncOptions though (too many options).  \r\n\r\nWhen I change the first field, I clear the value of the second.  loadOptions doesn't get called again until the user types in the field.  Until then, the list of options is wrong.\r\n\r\nShould I be getting a reference to the field and somehow reseting the options?  That wouldn't be very react-like, but this may be a strange corner case.  thoughts?"}}