CodePlexProject Hosting for Open Source Software
Which should be the more simple fluent option ?
The main difference is that, so far, there is only one entry point to test a value and it is 'Should'.
actual.Should().Satisfy(...) does not add value...
going to actual.Satisfy(...)
It is probably too late to change now, but I prefer ShouldSatisfy(...). Other than that minor point, I like the lambda approach.
actual.Should().Satisfy(...) sounds like more natural English. Without the Should in there, I think it should be actual.Satisfies(...).
Probably you are right but it is too late, the RC1 is out there.
Try to add an issue to change the name of the method to "Satisfies" and, if some user vote for it we can change it and release a beta or a RC2 instead the final release.
It should be actual.Should().Satisfy(
This is natural English and tries to keep a consistent entry point into the framework.
As I commented in the docs for Satisfy, it should really be Satisfies. I can see from the discussion above that the original idea was to have Should.Satisfy(). Grammatically this is consistent with the other assertions. Dropping "Should()" results
in an imperative verb instead of simple present tense - i.e. it looks like a command - "Satisfy! Do it!" rather than an assertion of what the thing *does* or should do.
Sorry Fabio, somehow missed the comment on Feb 16 regarding changing to "Satisfies" - doh!
yes... this thread is more than one year hold.
Are you sure you want to delete this post? You will not be able to recover it later.
Are you sure you want to delete this thread? You will not be able to recover it later.