-
Notifications
You must be signed in to change notification settings - Fork 260
Expand file tree
/
Copy pathdeferred.resolve.xml
More file actions
13 lines (12 loc) · 1.05 KB
/
deferred.resolve.xml
File metadata and controls
13 lines (12 loc) · 1.05 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
<entry name="deferred.resolve" type="method" return="Deferred">
<signature>
<added>1.5</added>
<argument name="args" type="Object">
<desc>
Optional arguments that are passed to the doneCallbacks.
</desc>
</argument>
</signature>
<desc> Resolve a Deferred object and call any doneCallbacks with the given <code>args</code>. </desc>
<longdesc> <p>When the Deferred is resolved, any doneCallbacks added by <a href="/deferred.then/"><code>deferred.then</code></a> or <a href="/deferred.done/"><code>deferred.done</code></a> are called. Callbacks are executed in the order they were added. Each callback is passed the <code>args</code> from the <code>.resolve()</code>. Any doneCallbacks added after the Deferred enters the resolved state are executed immediately when they are added, using the arguments that were passed to the <code>.resolve()</code> call. For more information, see the documentation for <a href="/category/deferred-object/">Deferred object</a>.</p> </longdesc>
</entry>