Task

using the Task's instance, we can cancel and running coroutines of this Task's scope. alternatively we can use the Task's cancel fun @see Task.cancel

Using the Task's instance, we can call complete.invoke passing in a ResultT if job succeeded or preferred Throwable ClientException as a failure result

using the Task's instance, we can call failure.invoke passing in a preferred Throwable ClientException as a failure result

Can be used to assign the task job while doing unit testing, not meant to be exposed or used in actual logic

This scope is used only created and used when invoking successUI and failureUI

using the Task's instance, we can call success.invoke and passing a success result

Number of tires to run the task , this will configured using TaskConfig.retry

Wait for the task to finish

Wait for the task to finish

cancels the current task's scope and invokes a cancelTask.

Wait for the task to finish it is a blocking call, if using it inside coroutine or suspended function use await instead

Wait for the task to finish it is a blocking call, if using it inside coroutine or suspended function use awaitOrNull instead

a cancel scope that is attachable to a task instance * task().onCancel { // Do this on cancel } use this scope to listen on the cancel response of a task

a task finished scope that is attachable to a task instance * task().onComplete {res, e -> // handle task completed } Use this scope to retrieve the end result of a task with a ResultT if succeed or ClientException if failed

Experimental callback to avoid adding switch threads logic, Also allow a chance to perform UI and background jobs after a task is done without dealing with multithreading

a failure scope that is attachable to a task instance * task().onFailure { // handle failure } use this scope to retrieve the failure response of a task

Experimental callback to avoid adding switch threads logic, Also allow a chance to perform UI and background jobs after a task is done without dealing with multithreading

a success scope that is attachable to a task instance * task().onSuccess { // do background logic , call another api } use this scope to retrieve the success response of a task

Experimental callback to avoid letting switch threads, Also allow a chance to perform UI and background jobs after a task is done without dealing with multithreading