Convert all AsyncTasks to Callables called from ReactiveX

[EmmanuelMess]

public class ReadFileTask extends AsyncTask<Void, Void, ReturnedValueOnReadFile> { to public class ReadFileTask implements Callable<ReturnedValueOnReadFile> {

and used as

final ReadFileTask task = new ReadFileTask(getContentResolver(), viewModel.getFile(), getExternalCacheDir(), isRootExplorer());

final Consumer<ReturnedValueOnReadFile> onAsyncTaskFinished = (data) -> {
//operations
}

final Consumer<? super Throwable> onError = error -> {
  error.printStackTrace();
}
Flowable.fromCallable(task)
  .subscribeOn(Schedulers.io())
  .observeOn(AndroidSchedulers.mainThread())
  .subscribe(onAsyncTaskFinished, onError);

[VishalNehra]

We seem to have a better solution now https://developer.android.com/topic/libraries/architecture/coroutines

So we use viewmodel like we normally would, and then something like viewModelScope.launch{} to launch a computation in that viewmodel. It'll be bound to it, so when viewmodel clears, the coroutine would be cancelled as well. We won't have to maintain it's state.

[EmmanuelMess]

We seem to have a better solution now developer.android.com/topic/libraries/architecture/coroutines

So we use viewmodel like we normally would, and then something like viewModelScope.launch{} to launch a computation in that viewmodel. It'll be bound to it, so when viewmodel clears, the coroutine would be cancelled as well. We won't have to maintain it's state.

I thought this as a step towards that.

[EmmanuelMess]

We seem to have a better solution now developer.android.com/topic/libraries/architecture/coroutines

So we use viewmodel like we normally would, and then something like viewModelScope.launch{} to launch a computation in that viewmodel. It'll be bound to it, so when viewmodel clears, the coroutine would be cancelled as well. We won't have to maintain it's state.

How does this deal with Context leaks?