Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

mattrjacobs
Copy link
Contributor

Otherwise, the only onErrors visible to RxJavaPlugins.errorHandler plugin are the ones which propagate all the way to SafeSubscriber.

…w onErrors.

* Otherwise, the only onErrors visible to plugin are the ones which propagate all the way to SafeSubscriber.
@cloudbees-pull-request-builder

RxJava-pull-requests #1206 SUCCESS
This pull request looks good

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does eventually emit the CompositeException. Is this consciously wanting to handle each error individually instead of only via the composite?

@mattrjacobs
Copy link
Contributor Author

@benjchristensen The goal of this pull request is to make the minimal set of calls to the plugin that ensures each onError is seen by the plugin handler at least once. In this case, I think it's fine to let the ErrorHandler see the CompositeException and handle all errors contained within. I just removed the plugin code from the mergeDelayError operator, to that effect.

@cloudbees-pull-request-builder

RxJava-pull-requests #1208 SUCCESS
This pull request looks good

benjchristensen added a commit that referenced this pull request Jun 2, 2014
…swallowing-operators

Hooked RxJavaPlugins errorHandler up within all operators that swallow onErrors
@benjchristensen benjchristensen merged commit 6417f0b into ReactiveX:master Jun 2, 2014
@benjchristensen benjchristensen mentioned this pull request Jun 3, 2014
@mattrjacobs mattrjacobs deleted the add-error-handler-to-error-swallowing-operators branch January 8, 2015 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants