Support Promise

[hh9527]

Will this project support Promise (which has already supported in Node 4.x)?

[stockholmux]

I don't believe that is on the roadmap. You can, however, promisify the library with bluebird.

There is even a specific example for this library.

[BridgeAR]

I do like to add a way to promisify the library if a certain parameter is passed. This won't be in the next release though.

[stockholmux]

@BridgeAR Interesting. If the option parameter is passed will it essentially just use bluebird? Or will it be implemented in a different way?

[BridgeAR]

Yes, I'd use bluebird internal.

[moretti]

Related project:
https://github.com/mjackson/then-redis

[luin]

As for me, it would be convenient to return a Promise if the last argument isn't a callback function. I implemented it in my redis client. Refer to https://github.com/luin/ioredis for more details.

Here's an example:

redis.get('foo', function (err, result) {
  console.log(result);
});

// Or using a promise if the last argument isn't a function
redis.get('foo').then(function (result) {
  console.log(result);
});

[BridgeAR]

That might be an option. I'll think about it when I have the time to tackle this.

[puzrin]

Probably it could be better for performance to return "thenable" instead of promise - no need to create promise wrapper for each item of chained commands. Wrapping will happen only on .then() call.

[Nepoxx]

While it would require a lot more work, I'd recommend using native promises instead of a library like bluebird. As much as I like bluebird, using it will increase the number of dependencies and isn't the only library used.

Mongoose uses native promises but allows replacing it with any promise implementation by the user, which is convenient for everyone. See http://mongoosejs.com/docs/promises.html#plugging-in-your-own-promises-library