Hugo Woodiwiss

@superjose I know this is quite old, but I think the problem you're having is because you don't have an ```#[options("")]``` for each endpoint, meaning your options requests are receiving...

I've added tests @richardszalay would you mind taking a look at this?

> Thanks for submitting this PR @hwoodiwiss, and apologies for taking so long to reply. > > I'll need to publish this as a major/breaking change release due to the...

@richardszalay I've been thinking it over, it might be easiest for now to remove the CallerArgumentExpression stuff, and add that later as a separate feature, what do you think?

I have been considering how this could also be further improved by the `CallerArgumentExpressionAttribute`, as this would give latitude to output the full expression of the matcher(s) that failed wouldn't...

@richardszalay Would you accept community contributions towards this, as I would be interested in working on this.

I've been considering the design of this. I was thinking of extending the definition of `IMockedRequestMatcher` to include a `Description` function, which can populated for each matcher type, and used...

In the current implementation in #92, the exception message looks like: ``` There are 1 unfulfilled expectations: Expected A request that matches: A URL matching: /test AND HTTP Method matching:...

That's how it works at the moment, it will only display information for configured matchers on an expected request. For example, a configuration that would yield my first example if...

Hi, just been looking at this a bit. Not sure if it's something Microsoft have done, however, it seems that building with msbuild 17 works. I used the command `$env:PackageVersion...