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
I have a DisposableObserver that has its own disposability implementation. It will correctly return the state when you hit isDisposed, but it is backed by a different enum (basically a fork of DisposableHelper, since it's internal-only). This is the delegate that TestObserver ends up wrapping in my test. Thing is, when you hit TestObserver#isDisposed(), it explicitly only does a reference comparison check between the disposable and the enum instance in DisposableHelper.
Is this intentional? If so, should isDisposed not be used with TestObserver in testing?
The text was updated successfully, but these errors were encountered:
Another note on this - this also seems to break isSubscribed checks. The delegate observer is disposed now, but the wrapping TestObserver is still subscribed
I have a DisposableObserver that has its own disposability implementation. It will correctly return the state when you hit
isDisposed
, but it is backed by a different enum (basically a fork ofDisposableHelper
, since it's internal-only). This is the delegate thatTestObserver
ends up wrapping in my test. Thing is, when you hitTestObserver#isDisposed()
, it explicitly only does a reference comparison check between the disposable and the enum instance inDisposableHelper
.Is this intentional? If so, should
isDisposed
not be used withTestObserver
in testing?The text was updated successfully, but these errors were encountered: