You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really excited to see support for attribute/prop selectors, but it feels like this is coding to the wrong abstraction. Under the hood JSX is javascript and this solution seems right if this was html.
Instead of a CSS selector why not supply an object of props to search for? <Foo foo="bar" /> => expect(wrapper.find({foo:"bar"})) => match <Foo foo="bar" blah="sheep" /> => expect(wrapper.find({foo:"bar"})) => match?
The text was updated successfully, but these errors were encountered:
From @hartzis:
I'm really excited to see support for attribute/prop selectors, but it feels like this is coding to the wrong abstraction. Under the hood JSX is javascript and this solution seems right if this was html.
Instead of a CSS selector why not supply an object of props to search for?
<Foo foo="bar" />
=>expect(wrapper.find({foo:"bar"}))
=> match<Foo foo="bar" blah="sheep" />
=>expect(wrapper.find({foo:"bar"}))
=> match?The text was updated successfully, but these errors were encountered: