Unused `unsubscribe` method on `CompletableUseCase` about android-clean-architecture-boilerplate

[qwertyfinger]

@DevKate In this case it's most probably a mistake.
I think CompletableUseCase should either hold the exact same logic as SingleUseCase:

fun execute(
        completableObserver: DisposableCompletableObserver, 
        params: Params
) {
        disposables.add(
            buildUseCaseObservable(params)
                .subscribeOn(Schedulers.from(threadExecutor))
                .observeOn(postExecutionThread.scheduler)
                .subscribeWith(completableObserver)
        )
    }

or return a Completable from execute() function and be stripped of subscription variable along with unsubcribe() function.
But in this case it's better to also have the same logic in SingleUseCase.

The choice between these two depends on whether you need to have access to a cold Observable in your Presenters (e.g. to combine them or apply some additional logic). I prefer using the latter in any case.
See this thread for more information.

Any example for CompletableUseCase?

[qwertyfinger]

@852dev Example usage? Saving some data to the database, for example. Anything where we don't need any actual data passed back to us, only the success/error status.