praeceptum

Results 4 issues of praeceptum

Releases **1.11** and **1.11.1** don't include **peview.exe**. Specifically: 1.11\Dependencies_x64_Debug.zip 1.11\Dependencies_x64_Release.zip 1.11\Dependencies_x86_Debug.zip 1.11\Dependencies_x86_Release.zip 1.11.1\Dependencies_x64_Debug.zip 1.11.1\Dependencies_x64_Release.zip 1.11.1\Dependencies_x86_Debug.zip 1.11.1\Dependencies_x86_Release.zip

Regarding the class `Moq.Tests.MatchersFixture`, given that the setups in the unit test method `MatchesIsInVariadicParameters()` are: ```csharp mock.Setup(x => x.Echo(It.IsIn(1, 2, 3, 4, 5))).Returns(1); mock.Setup(x => x.Echo(It.IsIn(6, 7, 8, 9, 10))).Returns(2);...

up-for-grabs
good first issue
stale

Would it be possible to add a member like `Returns(void)` to the Moq language so that void methods could chain a post-invocation `Callback(...)`? [![Back this issue](https://sponsorlink.blob.core.windows.net/public/separator.png "Back this issue")](https://www.devlooped.com/SponsorLink/github/issues/?s=devlooped) [![Back...

Should the documentation comments for `IVerifies.Verifiable()` and `IVerifies.Verifiable(string failMessage)` read: > mock.Setup( ... instead of: > mock.Expect( ... ? [![Back this issue](https://raw.githubusercontent.com/devlooped/SponsorLink/main/docs/assets/img/separator.png "Back this issue")](https://www.devlooped.com/SponsorLink/github/issues/?s=devlooped) [![Back this issue](https://img.shields.io/badge/backed-%240-EA4AAA?logo=githubsponsors "Back this...

bug