-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output promises customization #38
Conversation
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:
I'll get around to this this weekend. Awesome work, and thanks for putting in the effort! |
Great! I also wanted to do the config within No problem for Q, it can just be documented. Here is another concrete usage example. |
Did anyone ever end-up releasing a full Q integration as a module using the |
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). |
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.