Lines Matching refs:in

77 that executes asynchronously and completes at some point in the future.
150 > Deprecated in v2.6.0: Progress support is deprecated and should not be used anymore.
170 Once in the fulfilled or rejected state, a promise becomes immutable.
204 A promise makes the following guarantees about handlers registered in
284 Allows you to execute "cleanup" type tasks in a promise chain.
327 > Deprecated in v2.6.0: Progress support is deprecated and should not be used anymore.
342 of the promise that they are not longer interested in the result of an
352 further interest in the results of the operation.
412 > Deprecated in v2.8.0: External usage of `FulfilledPromise` is deprecated, use `resolve()` instead.
425 > Deprecated in v2.8.0: External usage of `RejectedPromise` is deprecated, use `reject()` instead.
438 > Deprecated in v2.8.0: LazyPromise is deprecated and should not be used anymore.
466 promise, all promises in the collection are cancelled. If the collection itself
486 [ExtendedPromiseInterface](#extendedpromiseinterface). If you pass in a custom
504 This can be useful in situations where you need to reject a promise without
514 Returns a promise that will resolve only once all the items in
516 will be an array containing the resolution values of each of the items in
526 resolved in the same way the first settled promise resolves.
534 Returns a promise that will resolve when any one of the items in
538 The returned promise will only reject if *all* items in `$promisesOrValues` are
550 Returns a promise that will resolve when `$howMany` of the supplied items in
573 value of a promise or value in `$promisesOrValues`.
632 These examples are contrived, of course, and in real usage, promise chains will
712 rejections will still forward handler results in a predictable way.
738 > Deprecated in v2.6.0: Progress support is deprecated and should not be used anymore.
741 **MUST** return a progress event to be propagated to the next link in the chain.
744 Also in the same way as resolutions and rejections, if you don't register a
748 to the next link in the chain. The best thing to do is to ensure your progress
751 This gives you the opportunity to transform progress events at each step in the
792 rethrown in an uncatchable way causing a fatal error.
839 wrapped in an exception of the type `React\Promise\UnhandledRejectionException`.