Allow setting up async methods easily about moq4 HOT 5 CLOSED

What's missing from the merged PR #60 to satisfy this?

from moq4.

I didn't know about those extensions. Those definitely help, although I guess they might be in the wrong namespace, as being extension methods they are not that easily discoverable because we typically do not add a using for Moq.Language.Flow (or is this where all extensions are defined?)

Do you think we should move them to just Moq namespace or will they pollute the main namespace unnecessarily?

Also, ideally, all methods that return Task or Task< T> should by default return a completed Task with the default value, instead of a null Task. With this last thing I believe Moq could be of great value also with async code.

from moq4.

Good point. Yes, the extension methods should be under Moq namespace.

+1 on the default value for Task. That should be an easy fix :)

/kzu

Daniel Cazzulino

On Tue, Dec 10, 2013 at 12:32 PM, jdom [email protected] wrote:

I didn't know about those extensions. Those definitely help, although I
guess they might be in the wrong namespace, as being extension methods they
are not that easily discoverable because we typically do not add a using
for Moq.Language.Flow (or is this where all extensions are defined?)

Do you think we should move them to just Moq namespace or will they
pollute the main namespace unnecessarily?

Also, ideally, all methods that return Task or Task should by default
return a completed Task with the default value, instead of a null Task.
With this last thing I believe Moq could be of great value also with async
code.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/64#issuecomment-30236958
.

from moq4.

Nice!

from moq4.

Closing this issue since all that it asked for has been implemented since.

from moq4.