Style Guide suggestion on Promises

[stacey-gammon]

I think we should be consistent in our use of native vs bluebird promises, as it can be confusing in the code to figure out which type is being used.

I'd like to propose that we add a style guide entry around this:

• Use native promises where ever possible and reasonable
• If you must use bluebird, and you are returning a Promise from an exported function, wrap it in a native promise. That way everyone can assume that a Promise returned from a function is of the native type.

Open for debate!

[epixa]

A million times, yes. Using bluebird is an implementation detail of a module, it shouldn't be exported directly otherwise the API of the module is the API of bluebird.

[Bargs]

Agreed. The styleguide should also recommend adding unit tests for this sort of API contract, otherwise it would be very easy to accidentally break.

[stacey-gammon]

Final decision: use native promises . More info on this discuss issue too: #13855

Closing, this is no longer active.