You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to use the retryWhen operator of the Completable I had problems understanding the behaviour detailed in it´s javadoc:
Returns a Completable which given a Publisher and when this Completable emits an error, delivers that error through an Observable and the Publisher should return a value indicating a retry in response or a terminal event indicating a termination.
Which highly differs from the documentation of Observable, Single and the docs, where the need of calling the provided observable's onNext/onError/onCompleted is more detailed:
Returns an Observable that emits the same values as the source observable with the exception of an {@code onError}. An {@code onError} notification from the source will result in the emission of a {@link Throwable} item to the Observable provided as an argument to the {@code notificationHandler} function. If that Observable calls {@code onComplete} or {@code onError} then {@code retry} will call {@code onCompleted} or {@code onError} on the child subscription. Otherwise, this Observable will resubscribe to the source Observable.
I could prepare a PR for both 1.x and 2.x versions if needed.
The text was updated successfully, but these errors were encountered:
Most people set up a flow inside the retryWhen so nobody calls onNext manually in there. However, the text should use a bit of a cleanup:
Returns a Completable which given a Publisher and when this Completable emits an error, delivers that error through a Flowable and the Publisher should signal a value indicating a retry in response or a terminal event indicating a termination.
While trying to use the
retryWhen
operator of the Completable I had problems understanding the behaviour detailed in it´s javadoc:Which highly differs from the documentation of Observable, Single and the docs, where the need of calling the provided observable's onNext/onError/onCompleted is more detailed:
I could prepare a PR for both 1.x and 2.x versions if needed.
The text was updated successfully, but these errors were encountered: