-
Q should send messages to the console when promises are manipulated so that a monitor like a Causeway logger or Web Inspector view can be attached.
The corresponding console API is not defined. This…
-
Say sth like the following
```
async.waterfall([
function(callback) {
User.find(req.body.friendId).complete(callback);
},
function(friend, callback) {
me.addFriend(friend).complete(call…
rjyo updated
11 years ago
-
Although I try very hard to avoid letting success values or rejections fall on the floor, I keep screwing up, and it seems like Q could help make it more obvious when I am screwing up.
The defer() re…
-
I just moved from jQuery deferred to when.js, but I block on this : I just discovered that when.js promises don't allow multiple args.
I know that I can pass an object, but it's far less readable tha…
-
So don't this the wrong way, but Q has major feature creepism. This project needs a good solid core that can be built off of. The core is there, but its mixed with a ton of unnecessary sugar and utili…
-
This work is already underway in the `promises_aplus` branch.
-
I'd like to be able to link to
```
http://promises-aplus.github.io/promises-spec/#3.2.6.1
```
thanks
-
One of the pitfalls of interacting with Promise-based APIs is the tendency for important errors to be silently swallowed unless an explicit rejection handler is specified.
For example:
``` javascrip…
-
`promise.always(fn)` is akin to a `finally` in a `try..catch..finally` block (although it can occur anywhere a Promise chain).
Originally envisioned as a shorthand for `promise.then(fn, fn)`, `promis…
-
EG, I want to be able to close this issue https://github.com/jden/resolved/issues/3 really easily. If I get around to it, I'll submit a pull request