Promise + pause + cancel + retry for Swift.
See ReactKit Wiki page.
// define task
let task = Task<String, NSError> { fulfill, reject, configure in
player.doSomething(completion: { (value: NSData?, error: NSError?) in
if error == nil {
fulfill("OK")
} else {
reject(error)
}
})
// pause/resume/cancel configuration (optional)
configure.pause = { [weak player] in
player?.pause()
}
configure.resume = { [weak player] in
player?.resume()
}
configure.cancel = { [weak player] in
player?.cancel()
}
}
// set success & failure
task.success { (value: String) -> Void in
// do something with fulfilled value
}.failure { (error: NSError?, isCancelled: Bool) -> Void in
// do something with rejected error
}
// you can call configured operations outside of Task-definition
task.pause()
task.resume()
task.cancel()
Notice that player
has following methods, which will work nicely with SwiftTask
:
doSomething(completion:)
pause()
(optional)resume()
(optional)cancel()
(optional)
One of the best example would be Alamofire (networking library) as seen below.
Using Alamofire
typealias AlamoFireTask = Task<String, NSError>
// define task
let task = AlamoFireTask { fulfill, reject, configure in
Alamofire.download(.GET, "http://httpbin.org/stream/100", destination: somewhere)
.response { request, response, data, error in
if let error = error {
reject(error)
return
}
fulfill("OK")
}
return
}
// set then
task.then { (value: String?, errorInfo: AlamoFireTask.ErrorInfo?) -> Void in
// do something with fulfilled value or rejected errorInfo
}
Task
can retry for multiple times by using retry()
method.
For example, task.retry(n)
will retry at most n
times (total tries = n+1
) if task
keeps rejected, and task.retry(0)
is obviously same as task
itself having no retries.
This feature is extremely useful for unstable tasks e.g. network connection.
By implementing retryable from SwiftTask
's side, similar code is no longer needed for player
(inner logic) class.
task.retry(2).success { ...
// this closure will be called even when task is rejected for 1st & 2nd try
// but finally fulfilled in 3rd try.
}
For more examples, please see XCTest cases.
Define your task
inside initClosure
.
let task = Task<NSString?, NSError> { fulfill, reject, configure in
player.doSomethingWithCompletion { (value: NSString?, error: NSError?) in
if error == nil {
fulfill(value)
} else {
reject(error)
}
}
}
In order to pipeline future task.value
or task.errorInfo
(tuple of (error: Error?, isCancelled: Bool)
) via then()
/success()
/failure()
, you have to call fulfill(value)
and/or reject(error)
inside initClosure
.
To add pause
/resume
/cancel
functionality to your task
, use configure
to wrap up the original one.
// NOTE: use weak to let task NOT CAPTURE player via configure
configure.pause = { [weak player] in
player?.pause()
}
configure.resume = { [weak player] in
player?.resume()
}
configure.cancel = { [weak player] in
player?.cancel()
}
Similar to then()
method, task.success(successClosure)
will return a new task, but this time, successClosure
will be invoked when task is only fulfilled.
This case is similar to JavaScript's promise.then(onFulfilled)
.
// let task will be fulfilled with value "Hello"
task.success { (value: String) -> String in
return "\(value) World"
}.success { (value: String) -> Void in
println("\(value)") // Hello World
return"
}
Just the opposite of success()
, task.failure(failureClosure)
will return a new task where failureClosure
will be invoked when task is only rejected/cancelled.
This case is similar to JavaScript's promise.then(undefined, onRejected)
or promise.catch(onRejected)
.
// let task will be rejected with error "Oh My God"
task.success { (value: String) -> Void in
println("\(value)") // never reaches here
return
}.failure { (error: NSError?, isCancelled: Bool) -> Void in
println("\(error!)") // Oh My God
return
}
See Retry-able section.
all(tasks)
is a new task that performs all tasks
simultaneously and will be:
- fulfilled when all tasks are fulfilled
- rejected when any of the task is rejected
zip(task1, task2)
is a new task that perform each task simultaneously. Difference with all(_ tasks)
is each tasks could have different generic types.
allSettled(_ tasks)
is a new task that perform each task simultaneously. returned newTask is always fulfilled state even if any tasks rejected. You can check what task is fulfilled or rejected by Settled object.
- SwiftTask(Promise拡張)を使う - Qiita (Japanese, ver 1.0.0)