You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's becoming more and more common for libraries not to support providing a promise library. In addition, it's not safe to overwrite or extend the native global Promise.
Instead it may be better to think of these extended promise methods as a utility belt similar to lodash.
You can this today; however, it is verbose and creates an extra Promise allocation.
It's becoming more and more common for libraries not to support providing a promise library. In addition, it's not safe to overwrite or extend the native global
Promise
.Instead it may be better to think of these extended promise methods as a utility belt similar to lodash.
You can this today; however, it is verbose and creates an extra
Promise
allocation.One approach is to make the helper methods high-level and auto-currying. It would be a breaking change because values would go last. E.g.,
Long chains are probably good the way they are. But, we may want
.thru
or.toPromise
methods to get a native promise back.The text was updated successfully, but these errors were encountered: