-
-
Notifications
You must be signed in to change notification settings - Fork 697
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
fixing #239 (without changing chai.js) #244
Conversation
leider
commented
Feb 9, 2014
- hope this is better
Much better! Unfortunately, not quite ready yet. I think you will have an issue if no match is found. The best way is to add assertions that fail using PS: No need to open a new PR this time, you can just append to this one. |
done. :) Thx for the eagle eyes |
done again |
Hi, did you forget about this one? :) |
fixing #239 (without changing chai.js)
Any timeline on merging this? #239 is the only thing preventing me from upgrading :( |
@adambiggs it is already merged. I don’t know why #239 is still open and why there was no patched version released. |
@lo1tuma oops, I meant to ask about publishing this to NPM... 😕 |
@logicalparadox can you release a patched version on npm? |
Released in |
Thanks! 🍻 |