Issue #200 - calling loadAsyncOptions when receiving new props #360
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
|
Thanks for the fix @drfeelgoud! much appreciated. |
JedWatson
added a commit
that referenced
this pull request
Aug 8, 2015
Issue #200 - calling loadAsyncOptions when receiving new props
Collaborator
|
@JedWatson - can you hold off on 0.6.1 (PR #355) for a little longer - I've spotted a bug with the fix for requesting asyncOptions again on value change - PR on the way 😄 |
Contributor
Author
|
Happy to help, thanks for merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves issue #200
When passing new props to component, asyncOptions are fetched, because the passed values are not guaranteed to be contained in the current options cache.