Only send error event if not from cancelling the task #21
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.
Closes #20.
Upon cancelling a Kingfisher task, the Kingfisher library calls the completion block twice:
This causes issues in Rx because it detects a re-entrancy anomaly. I'm not actually sure if it causes a real issue given that the task is being cancelled from the stream being disposed of anyway, but it prints a scary message to the console and it's best to clean things up.
Important note: I don't have enough familiarity with the Kingfisher library to be confident that there's no time they would only send the task cancelled error and not from us explicitly calling
task.cancel()
. If that were ever to happen, we would want to re-think this solution.