-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix observeOn() invocation order. #67
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
Conversation
@omo can you post your test to the pull request as well so I can pull it down and help you with robolectric? It is important that we have tests that specify these kinds of behaviours as we decide on them. Thanks! |
@dpsm Well, I should've tried a bit harder. A quick googling told me that Robolectric has a way a way to pump the event loop. Added tests. PTAL? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this is exactly what I wanted here. Thanks for the tip! Updated.
This needs a rebase now. |
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this right? I thought it moved to rx.android.internal
.
It should be called before lift() so that the operator can observe it on the main thread. This change also adds some test for other bindXx() variants to get better coverage.
Oops. I left some change uncommitted. Sorry about that. It should be fixed now. |
Ping? This is a regression fix with test. Travis build is green :-) |
Fix observeOn() invocation order.
LGTM 👍 |
Thanks! |
It should be called before lift() so that the operator can observe it on the main thread.
I tried to write a test but it didn't work, presumably because Robolectric doesn't have an event loop?