-
Notifications
You must be signed in to change notification settings - Fork 494
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
Wrong emit order (Loading after Success) #76
Comments
My current workaround is to add a small delay to the observable:
|
@chrisbanes Can you try to debug there? |
Yep I saw the code but haven't had a chance to step back into MvRx yet (I won't be able to until Monday now). |
This test also passes. If this could be reproduced with a failing test, that would be great. |
Closing this. I can't recreate in tests, and I think I've worked out a bug in my app which is causing this. Thanks! |
I've noticed a bit of weirdness since moving to MvRx. After debugging it today, it turns out that the emitting order using
execute()
is wrong for Observables which emit immediately:imageProviderObservable in this instance is a
BehaviorSubject
with a default value, so will always emit immediately on subscribe. If the Observable does not emit again, the final state isLoading
which is obviously wrong.The text was updated successfully, but these errors were encountered: