Returning null

[mwereda]

I added two methods that configure method call to return null:

1. ReturnNull()
2. ReturnNullForAnyArgs()

Using one of these methods allows to write more easily code - instead of using
something.SomeAction().Returns(i=> null) it can be written that way: something.SomeAction().ReturnsNull().
With intellisense it's much easier to write call that should return null. In my opinion it's also much more verbose.

I've placed both methods in separate namespace so main namespace doesn't have too much mtehods.

[veihan]

overkill?

[mwereda]

I think it's not overkill.
Sometimes you need/want stub's method to return null and write logic that deal with that null. With my team we've created extension method ReturnsNull and it's much faster for us to use it instead of writing something.SomeAction().Returns(i=> null). Especially when you user R# pressing R and N keys and Enter after that - it speeds code writing a little bit up.

I'm aware that this could be not mostly used method. That's why I've placed it in another namespace.

[veihan]

Ok.

Btw. R# as R language, ported to C# ex. R.NET?

[mwereda]

@veihan - I meant ReSharper

[veihan]

lol

[veihan]

I'm a nice guy mostly, so don't get me wrong here. This has already been discussed and it was answered by @dtchepak in late 2012 (read it #87) and generally the idea was rejected.
I'm recommending to use function:
OrderBy(x => check all issues of NS).ThenBy(x => collaborate).ThenBy(x => fix, change).

[mwereda]

Hi, any chances to add this CR to NSubstitute codebase?

[dtchepak]

Hi Michal,
Sorry for the delay in getting back to you. I've included this in release 1.8.2. Thanks for the contribution.

As an aside I'm wary of including many more extensions like this; I want to avoid the situation where people find NSub works differently than they expect because there are fewer imports than a code sample they look at. I've let this one through just because it has kept coming up. :)

Cheers,
David