Todd Menier

A FlurlRequest should never be reused. Much like the HttpRequestMessage that it effectively wraps, it's underpinned by a forward-only stream. The rules mirror those of the HttpClient stack: reuse clients...

I'm not sure if I'm following. Any value set _explcitly_ on HttpTest.Settings should always override the same setting set anywhere in the SUT. That's by design. But when not explicitly...

Got it. I probably should have ran your test before replying. :) Sounds legitimate, it's been added to the backlog and I'll look into when I get some time.

Thanks for reporting, appears to be legit.

Thank you for this library. I'm evaluating whether it could be useful for my purposes, and upon reading the readme I think the most obvious question was, where do I...

Thanks. I'll look at this more closely when I have some time, but I like the general idea. I'm wondering if a `FlurlRequest` arg instead of `FlurlCall` might be enough?...

New features are more than just a merge. I haven't had time to work on the next sprint so you'll have to be patient or use your own fork.

Hmm. It seems impossible that Flurl is constructing that message. Here's the only line in the entire code base where Flurl builds a message resembling that: https://github.com/tmenier/Flurl/blob/dev/src/Flurl.Http/FlurlHttpException.cs#L42 Note that `call.Response.StatusCode`...

Haha, ok I'll keep this open. I like your idea of falling back on the enum value, should be simple and I'll get it on my near-term radar.

I honestly don't think what you're asking for is possible. Opting in to Newtonsoft happens at runtime so it can't be known at compile time. I understand the footprint is...