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
As far as I can tell, Should().Contain() uses Equals() to compare objects. It would be nice to be able to combine Should().Contain() and Should().BeEquivalent() and leverage structural equality instead.
We already have ShouldAllBeEquivalentTo(), this could be called ShouldSomeBeEquivalentTo() or ShouldContainEquivalentOf().
Thanks for this awesome library !
The text was updated successfully, but these errors were encountered:
You can build your own extension that passes each object in the collection to a call to ShouldBeEquivalenTo to compare each object with the one you like to find. At least one of those objects in the collection must match.
As far as I can tell,
Should().Contain()
usesEquals()
to compare objects. It would be nice to be able to combineShould().Contain()
andShould().BeEquivalent()
and leverage structural equality instead.We already have
ShouldAllBeEquivalentTo()
, this could be calledShouldSomeBeEquivalentTo()
orShouldContainEquivalentOf()
.Thanks for this awesome library !
The text was updated successfully, but these errors were encountered: