-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
matcher for is
#97
Comments
👍 from me |
Shouldn't |
"match" implies a selector/regex, and possibly multiple elements. is/be imply one exact identity. |
The Assuming that PR is merged, you'll be able to make assertions like: expect(foo).to.match('div')
expect(foo).to.match('div.some-class')
expect(foo).to.match('MyComponent')
expect(foo).to.match(MyComponent) That being said, I do agree that something like |
I tried
expect(foo).to.be.a('bar')
to be a nicer form ofexpect(foo.is('bar')).to.equal(true)
, but it didn't work. What do you all think about a matcher for this?The text was updated successfully, but these errors were encountered: