Fix custom indicator may not stop on error #37
Merged
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
dreampiggy changed the title dreampiggy changed the title 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 Indicator ViewBuilder should be called once, because we associatedBindinginto the arg, not a callback function to create same view multiple times.Reverted this change in 4097d56. See reason in #38
Fix one issue that indicator does not stop on error, because the
.imageis always non-nil. For our built-in activity/progress indicator, it handles theisAnimatingbinding object, and may stop. But however, some custom indicator view may not use this. We don't rely on this now.