-
Notifications
You must be signed in to change notification settings - Fork 1
async.Deferred.Promise
Note: Deferred.Promise
cannot be constructed directly; instances are obtained by applying then()
to other native promises or Deferred
objects.
var p = promise.then(
function (value) { ... },
function (error) { ... },
function (value) { ... }
);
Associates callback, errback and a progress handler with a promise; returns a dependent promise. Any of the arguments
may be omitted or replaced with null
; calling then()
without arguments simply issues a dependent promise
without associating any callbacks.
var p = promise.then(deferred);
Makes deferred
, which must be an instance of Deferred.Promise
— foreign implementations or dependent promises
are not accepted — into a dependent promise, and returns it as the result. The canceller associated with the deferred
will never be called as it is no longer the root of the chain. Effects of calling resolve()
or reject()
on
deferred
after it's been passed into then()
are unspecified.
The net effect of the sequence:
var deferred = new Deferred();
// a sequence of calls to deferred.then() and deferred.done()
var p = promise.then(deferred);
is equivalent to:
var deferred = promise.then();
// a sequence of calls to deferred.then() and deferred.done()
var p = deferred;
A function that will be called in the event the promise is resolved, receiving as its only argument the value, which is never another promise, that the promise has been resolved to. Resolving a promise executes all callbacks that's been associated with it through calls to then()
and done()
in a non-specified order. As a result of its execution, the callback may:
- Return a defined, non-promise value. In this case, the dependent promise (if any) will be resolved to this value.
- Return an
undefined
value (or, equivalently, not return a value i.e. fall off the end or execute an emptyreturn
). In this case, the dependent promise (if any) will be resolved to the same value as was passed into the callback. - Return a promise value. In this case, the dependent promise (if any) will now be treated as a dependent of the returned promise, i.e. it will not be resolved or rejected immediately but only upon resolution or rejection of the promise returned by the callback.
- Throw a non-promise value. In this case, the dependent promise will be rejected with this value. Note that throwing an exception creates a separately tracked rejection which, if unhandled, may cause an uncaught exception to be thrown.
- Throw a promise value. In this case, the dependent promise will be rejected when the returned promise is either resolved or rejected, with the value that the latter is resolved to or rejected with.
If callback is not specified and the dependent promise exists, the latter is resolved to the same value as the argument that the callback would have received.
A function that will be called in the event the promise is rejected, receiving as its only argument the value, which is never another promise and typically an Error
or other exception object, that the promise has been rejected with. Resolving a promise executes all errbacks that's been associated with it through calls to then()
and done()
in a non-specified order.
The errback is executed in the same way as the callback with two important differences in treatment of its execution results:
- Returning an
undefined
value by the errback will cause the dependent promise to be rejected with the same value as was passed into the errback. Errback returningundefined
is not considered to have handled the rejection. - Any other result of errback's execution (even if it throws an exception of its own) is counted as handling the rejection.
If errback is not specified and the dependent promise exists, the latter is rejected with the same value as the argument that the callback would have received.
A rejection is considered unhandled if, by the time all dependency chains are exhausted it was not handled by any errback. Any rejections — those resulting from a call to Deferred.reject()
as well as those resulting from exceptions raised by callbacks and errbacks — that are still unhandled at the time the synchronous part of Deferred.resolve()
, Deferred.reject()
or Deferred.cancel()
finishes executing are either ignored or passed to the user-supplied handler or to ice.uncaught()
, depending on the arguments passed into the respective call. Note that ice.uncaught()
may throw exceptions that would not be caught by any try
-block.
Please note, that it is in general impossible to synchronously determine whether a rejection may still be handled in the future:
var a = new Deferred();
a.reject("later");
a.done(null, function (error) {...});
is conceptually a perfectly valid sequence that would indeed executed an errback, but since it is associated with the promise only after the call to reject()
completes, the latter has no choice but treat it as an unhandled exception. Use custom handling or outright suppression of unhandled rejections to in these situations; the default choice is to signal them as errors.
The progress handler is called as a result of executing Deferred.progress()
on the root deferred. It is passed the same argument as the original call to Deferred.progress()
which should not be a promise. Any results returned or exceptions thrown by the progress handler are ignored.
promise.done(
function (value) { ... },
function (error) { ... },
function (value) { ... }
);
or
promise.done(deferred);
Fully identical to then()
except that it does not return a dependent promise, making it a somewhat more efficient
alternative when the dependent promise value is not needed. It is possible to call done()
without arguments but the
resulting sub-chain will not handle rejections and may cause uncaught exceptions should one occur.
These helpers are trivial wrappers on top of then()
and done()
. They are added here for convenience or compatibility with other packages. Their definitions:
// ...
thenBoth: function (callback) {
return this.then(callback, callback);
},
doneBoth: function (callback) {
this.done(callback, callback);
},
"catch": function (errback) {
return this.then(null, errback);
},
finalCatch: function (errback) {
this.done(null, errback);
}
// ...
Both xxxBoth()
versions attach one callback as both a regular callback and an errback. Usually it is used for a general cleanup regardless of a result of an asynchronous operation.
Both catch()
and finalCatch()
attach a single errback without a callback. It is there mostly for compatibility with ES6's Promise.
doneBoth()
and finalCatch()
use done()
in their implementation and are meant to be the last link in a processing chain, while thenBoth()
and catch()
use then()
, and return a promise to continue a chain.
var p = promise.protect();
Returns a dependent promise cancellation of which will never lead to a cancellation of the original promise.
promise.cancel(reason, catchUnhandled);
Cancels the promise, leading to a rejection of its direct dependents. Also cancels the parent promise if it has no other dependents. Overall, the effects of the cancellation must be equivalent to the following:
- Find the nearest ancestor of the cancelled promise that has more than one direct dependent, or, failing that, the root Deferred;
- If a root Deferred was found (note that this implies that it has at most one direct dependent which must lead to the cancelled promise or otherwise it is the cancelled promise), execute its canceller callback if one was set at construction, passing in
reason
if supplied, or an instance ofDeferred.CancelError
. An exception thrown by the canceller is treated as an unhandled rejection, any other result is ignored; - Execute all errbacks found upstream of the cancelled promise and downstream of the ancestor promise found during the first step, ignore any results they may return or exceptions they may throw; if
reason
was supplied in the call tocancel()
pass it as the argument into the errbacks, otherwise pass an instance ofDeferred.CancelError
; - Reject the cancelled promise with
reason
supplied in the call or with an instance ofDeferred.CancelError
ifreason
was not supplied.
The optional argument catchUnhandled
may take one of the following values:
- A falsy value, or omitted: any unhandled rejections will be passed to
ice.uncaught()
and potentially raise an unhandled exception. - A truthy non-function value: the unhandled rejections are ignored.
- A function accepting a single argument: will be called for every unhandled rejection receiving the associated value.