We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I personally expected
expect(object).to.have.property(key, value);
to behave just like
expect(object).to.have.property(key); expect(object[key]).to.eql(value);
but it does ".equal(value)" instead. Which one is the right behaviour?
The text was updated successfully, but these errors were encountered:
My expectation is the current behaviour, but I can see an argument for either. I have submitted pull request #123 which allows syntax like this:
expect(object).to.have.property(key).which.eql(value);
But I think the original author has ceased development on this project. I'm considering my own fork.
Sorry, something went wrong.
make have.property to check equality of the value unstrictly
b52297b
closes Automattic#124
Cool. I quess you are right. Thank you.
I just now discovered how stale the repo really is. Well, I already did the PR so... whatever, @guille.
Successfully merging a pull request may close this issue.
I personally expected
to behave just like
but it does ".equal(value)" instead. Which one is the right behaviour?
The text was updated successfully, but these errors were encountered: