Adam Rodger

@mefellows the preferred approach is to create a ticket to propose an API so that we can discuss prior to implementing. That way we can make sure we're all on...

I think the problem with that is it only lets you upload one part. Multi-part bodies can contain many parts, some of which may be files and some may be...

So here's how I'm doing it at the moment, which shows that bodies can contain many parts (this is a made up example so as not to copy real code...

Yeah we'd probably have to make core changes to support that, but we can't really add it to PactNet until that's done because otherwise it would be an incomplete solution...

Yeah that would be a breaking change because the return type of that would have to be void to prevent people trying to add a second file, because that would...

What we could try to do is something like a half way house which only allows you to specify a file and nothing else, e.g. instead of `WithJsonBody` you'd have...

One thing that stands out in my mind is the content length of such a request. The user is allowed to specify any headers they want, so they can specify...

PactNet has to pick and use one serialiser internally because there are internal implementation details which require control of how things like matchers are serialised. That means that currently Newtonsoft...

Replaced with RFC: https://github.com/pact-foundation/pact-net/issues/458

My design notes above are specifically about how the FFI library is wrapped in .Net. Everything is at `internal` accessibility level and is not accessible to any third party assembly/project....