class ObservableUseCase.class ObservableUseCase.class CompletableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.class CompletableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.interface CompletableDisposablesOwner interface.interface CompletableDisposablesOwner interface.class CompletableUseCaseConfig.Builder to construct this object.class FlowableUseCase, class SingleUseCase,
class CompletableUseCase, class ObservableUseCase, class MaybeUseCase use cases and automatically add
resulting disposables to one composite disposable. You may find handy to implement
this interface in custom Presenters, ViewHolders etc.CompletableUseCase.execute method has already been called
on this instance of class CompletableUseCase, previous one is disposed,
no matter what current state of internal Completable is. This behavior
can be disabled by passing false to CompletableUseCaseConfig.disposePrevious
method.CompletableUseCase.execute method has already been called
on this instance of class CompletableUseCase, previous one is disposed,
no matter what current state of internal Completable is. This behavior
can be disabled by passing false to CompletableUseCaseConfig.disposePrevious
method.CompletableUseCase.execute method has already been called
on this instance of class CompletableUseCase, previous one is disposed,
no matter what current state of internal Completable is. This behavior
can be disabled by passing false to CompletableUseCaseConfig.disposePrevious
method.CompletableUseCase.execute method has already been called
on this instance of class CompletableUseCase, previous one is disposed,
no matter what current state of internal Completable is. This behavior
can be disabled by passing false to CompletableUseCaseConfig.disposePrevious
method.FlowableUseCase.execute method has already been called
on this instance of class FlowableUseCase, previous one is disposed,
no matter what current state of internal Flowable is. This behavior
can be disabled by passing false to FlowableUseCaseConfig.disposePrevious
method.FlowableUseCase.execute method has already been called
on this instance of class FlowableUseCase, previous one is disposed,
no matter what current state of internal Flowable is. This behavior
can be disabled by passing false to FlowableUseCaseConfig.disposePrevious
method.FlowableUseCase.execute method has already been called
on this instance of class FlowableUseCase, previous one is disposed,
no matter what current state of internal Flowable is. This behavior
can be disabled by passing false to FlowableUseCaseConfig.disposePrevious
method.FlowableUseCase.execute method has already been called
on this instance of class FlowableUseCase, previous one is disposed,
no matter what current state of internal Flowable is. This behavior
can be disabled by passing false to FlowableUseCaseConfig.disposePrevious
method.MaybeUseCase.execute method has already been called
on this instance of class MaybeUseCase, previous one is disposed,
no matter what current state of internal Maybe is. This behavior
can be disabled by passing false to MaybeUseCaseConfig.disposePrevious
method.MaybeUseCase.execute method has already been called
on this instance of class MaybeUseCase, previous one is disposed,
no matter what current state of internal Maybe is. This behavior
can be disabled by passing false to MaybeUseCaseConfig.disposePrevious
method.MaybeUseCase.execute method has already been called
on this instance of class MaybeUseCase, previous one is disposed,
no matter what current state of internal Maybe is. This behavior
can be disabled by passing false to MaybeUseCaseConfig.disposePrevious
method.MaybeUseCase.execute method has already been called
on this instance of class MaybeUseCase, previous one is disposed,
no matter what current state of internal Maybe is. This behavior
can be disabled by passing false to MaybeUseCaseConfig.disposePrevious
method.ObservableUseCase.execute method has already been called
on this instance of class ObservableUseCase, previous one is disposed,
no matter what current state of internal Observable is. This behavior
can be disabled by passing false to ObservableUseCaseConfig.disposePrevious
method.ObservableUseCase.execute method has already been called
on this instance of class ObservableUseCase, previous one is disposed,
no matter what current state of internal Observable is. This behavior
can be disabled by passing false to ObservableUseCaseConfig.disposePrevious
method.ObservableUseCase.execute method has already been called
on this instance of class ObservableUseCase, previous one is disposed,
no matter what current state of internal Observable is. This behavior
can be disabled by passing false to ObservableUseCaseConfig.disposePrevious
method.ObservableUseCase.execute method has already been called
on this instance of class ObservableUseCase, previous one is disposed,
no matter what current state of internal Observable is. This behavior
can be disabled by passing false to ObservableUseCaseConfig.disposePrevious
method.SingleUseCase.execute method has already been called
on this instance of class SingleUseCase, previous one is disposed,
no matter what current state of internal Single is.
Use Single.executeStream if you want to run one
class SingleUseCase multiple times simultaneously. This behavior
can be disabled by passing false to SingleUseCaseConfig.disposePrevious
method.SingleUseCase.execute method has already been called
on this instance of class SingleUseCase, previous one is disposed,
no matter what current state of internal Single is.
Use Single.executeStream if you want to run one
class SingleUseCase multiple times simultaneously. This behavior
can be disabled by passing false to SingleUseCaseConfig.disposePrevious
method.SingleUseCase.execute method has already been called
on this instance of class SingleUseCase, previous one is disposed,
no matter what current state of internal Single is.
Use Single.executeStream if you want to run one
class SingleUseCase multiple times simultaneously. This behavior
can be disabled by passing false to SingleUseCaseConfig.disposePrevious
method.SingleUseCase.execute method has already been called
on this instance of class SingleUseCase, previous one is disposed,
no matter what current state of internal Single is.
Use Single.executeStream if you want to run one
class SingleUseCase multiple times simultaneously. This behavior
can be disabled by passing false to SingleUseCaseConfig.disposePrevious
method.class FlowableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.class FlowableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.interface FlowableDisposablesOwner interface.interface FlowableDisposablesOwner interface.class FlowableUseCaseConfig.Builder to construct this object.class MaybeUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.class MaybeUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.interface MaybeDisposablesOwner interface.interface MaybeDisposablesOwner interface.class MaybeUseCaseConfig.Builder to construct this object.class ObservableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.class ObservableUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.interface ObservableDisposablesOwner interface.interface ObservableDisposablesOwner interface.class ObservableUseCaseConfig.Builder to construct this object.class SingleUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.class SingleUseCase use cases
and automatically add resulting disposables to one composite disposable. You
may find handy to implement this interface in custom Presenters, ViewHolders etc.interface SingleDisposablesOwner interface.interface SingleDisposablesOwner interface.class SingleUseCaseConfig.Builder to construct this object.