Output promises customization

[sebv]

Current output promizes only have a then method added to the chai object. This does not change the default behavior, but optionally enable better integration with Q or other custom promise environment.

see #37.

[domenic]

Thanks! I agree providing something like this is a good idea. I'll use your code as the basis for it. However, I'll be making a few modifications:

• There will be no built-in support for Q, and thus no string overload to promisifyWith or promisifyMethods property. You can publish a Q + Chai as Promised integrator as its own npm package!
• The method promisifyWith will exist on the chaiAsPromised object, not on the chai object.

I'll get around to this this weekend. Awesome work, and thanks for putting in the effort!

[sebv]

Great!

I also wanted to do the config within chai-as-promised, but could not see an easy way to do it, since there seem to be no state.

No problem for Q, it can just be documented.

Here is another concrete usage example.

[domenic]

Merged as 6eba483, revised in cb59ba9, and released as 4.1.0. Thanks!

[geekytime]

Did anyone ever end-up releasing a full Q integration as a module using the transferPromiseness approach?

[sebv]

Probably not yet, here is an example of integration.

I think if you try to mixin the full Q api, there are a few naming collisions (like keys).