Skip to content
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

Merged
merged 5 commits into from
Feb 25, 2014
Merged

fixing #239 (without changing chai.js) #244

merged 5 commits into from
Feb 25, 2014

Conversation

leider
Copy link
Contributor

@leider leider commented Feb 9, 2014

  • hope this is better

@logicalparadox
Copy link
Member

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 err(function() { .... For each assertion you add in test/expect.js you should also have an assertion that fails wrapped with that pattern.

PS: No need to open a new PR this time, you can just append to this one.

@leider
Copy link
Contributor Author

leider commented Feb 9, 2014

done. :) Thx for the eagle eyes

@leider
Copy link
Contributor Author

leider commented Feb 9, 2014

done again

@leider
Copy link
Contributor Author

leider commented Feb 23, 2014

Hi, did you forget about this one? :)

logicalparadox added a commit that referenced this pull request Feb 25, 2014
fixing #239 (without changing chai.js)
@logicalparadox logicalparadox merged commit 4e25ff0 into chaijs:master Feb 25, 2014
@adambiggs
Copy link

Any timeline on merging this? #239 is the only thing preventing me from upgrading :(

@lo1tuma
Copy link
Contributor

lo1tuma commented Mar 14, 2014

@adambiggs it is already merged. I don’t know why #239 is still open and why there was no patched version released.

@leider leider deleted the fix_for_contains branch March 14, 2014 16:44
@adambiggs
Copy link

@lo1tuma oops, I meant to ask about publishing this to NPM... 😕

@lo1tuma
Copy link
Contributor

lo1tuma commented Mar 19, 2014

@logicalparadox can you release a patched version on npm?

@logicalparadox
Copy link
Member

Released in 1.9.1. View release notes.

@lo1tuma
Copy link
Contributor

lo1tuma commented Mar 19, 2014

Thanks! 🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants