Provide more intuitive methods about nsubstitute HOT 3 OPEN

Hi @BenjaminAbt ,

Sorry for the delayed response.
If you have the time would you be happy to send your branch as a PR?

A few notes on the existing commit:

• I'd prefer to avoid ReceiveAtLeast. We already dump so much into intellisense with extension methods on Object and I'd prefer not to exacerbate the problem. 😅
• I think we only call Quantity.Matches with a List, so Count() would probably end up being more efficient than something like .Take(minInclusive).Count() for this case. Any thoughts on whether we should change Matches to take a list to make this more obvious?
• Did you want to add any of AtMost, LessThan, MoreThan as well?
• Existing problem, but if you do send through a PR would you also be able to add code docs to the public members of Quantity that are currently missing doc comments?

As per @304NotModified's reply, if you have other specific examples please create an issue/s for them. 👍

from nsubstitute.

I like the idea here, but IMO this GitHub issue is very broad and therefore hard to fix.

people no longer had to google workarounds.

I don't know what this exactly means, other than the given examples

from nsubstitute.

I like the idea here, but IMO this GitHub issue is very broad and therefore hard to fix.

Yes, that was the intention. I wanted to find out what the general attitude was before I put more time into it; also because there have been statements about it in the past (see above).

If you have the time would you be happy to send your branch as a PR?

For sure.

I'd prefer to avoid ReceiveAtLeast. We already dump so much into intellisense with extension methods on Object and I'd prefer not to exacerbate the problem.

Yes, I understand this, but I see devs struggling. IntelliSense is just normal in our .NET / Visual Studio ecosystem, and I just see developers browsing IntellISense instead of people looking at the docs. It's not a one-off thing either, I see it consistently.

Did you want to add any of AtMost, LessThan, MoreThan as well?

Sounds good.

Existing problem, but if you do send through a PR would you also be able to add code docs to the public members of Quantity that are currently missing doc comments?

Yes.

I don't know what this exactly means, other than the given examples

There is one thing I do differently now and recommend to other people: use CHatGPT instead of GitHub Copilot to migrate from Moq to NSubstite.

The results are better and people need less help with things they can't find the equivalent for.
GitHub Copilot has sometimes suggested things for NSubstite that correspond to Moq's API - of course that doesn't work because they dont exist.

from nsubstitute.