-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CombineLatestDelayError emits error before all inner observables emit result #4414
Comments
Your |
Docs state:
So empahsis is on:
In this scenario second observable is not finished and error is not delayed. What if you want to make two API calls no matter of the result of previous and combine their result? I do understand that there is always different type of solution and approach but I just believe that either docs are not correct or this is potential bug since it should behave as stated. |
The documentation is incorrect as there is no "outer |
This is more complicated to work out the proper rules. For example, what should happen if you |
For For second, I would say I'm just following up with an idea, its not that I expect it to work that way. |
|
/cc @zsxwing |
Sorry for the delay. Once RC3 is released, I'll look into it and work out the details. |
I've considered many alternatives and can give you a reasonable workaround: apply |
I spent a considerable amount of time on this and was unable to come up with a reasonable way for changing |
Recently I came across following issue while using
combineLatestDealyError
operator. This code has been tested on Android, Nexus 5x running OS 6.0.1.This piece of code is trying to simulate callbacks using delays - for example Android Pay availability callback.
Problem here arises once this code is run. The log will be:
This is quite contradictory to the docs that state that expected behavior should be:
The expected result does happens if you add
subscriber.onNext(true)
to theerrorObservable
beforesubscriber.onError...
The text was updated successfully, but these errors were encountered: