Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove have(n).items matchers #293
@samphippen I agree with you, we should merge this PR only after having the external gem. I already created a local git repo for that gem in my machine, meanwhile, I already talked to @myronmarston and he's setting up a repo for that gem to live in.
After the he set this up, I'll send the code to that github repo and I'll ask for some code review from you guys.
referenced this pull request
Jul 23, 2013
"ready" is such a generic goal, though. Software is never done and is always changing.
I'd say I'm OK merging this and the autotest PR once the new gem is to a place where we're 100% sure that the removal is going to work out OK. Are there any lingering issues for either?
If not, we can go ahead and merge these.
I already finished the first PR in https://github.com/rspec/rspec-collection_matchers and the have(n) matchers are already in its master branch. But, although I've finished the PR, there's at least 2 must have that I still want to finish to call it a 0.1 version: