Todd Menier

Sorry for the long delay. It turns out this wasn't an oversight. Flurl relies on async methods off `HttpContent` to implement these methods, and those [didn't support](https://github.com/dotnet/runtime/issues/916) CancellationTokens until .NET...

@Decimation @whl2606555 This issue wasn't a high priority relative to the roadmap. But it's an easy one, so if it's causing you pains and you're willing to use a prerelease...

Can you help me understand if using Flurl in a project where nullable reference types are enabled may cause actual problems? Is it just that nullable types have a certain...

I'll add this to the backlog. > You can see that nullable reference types isn't just self-documenting feature. I'm not sure I agree. Both examples above demonstrate the same basic...

@Tunduk Also I appreciate your offer to help! That would be great, but I would say don't start quite yet. I'm catching up on a few things and will be...

I'm not sure what you mean by "generate a warning". Are you suggesting Flurl should throw an exception if you pass a string to PostJsonAsync?

I don't think the documentation is inadequate. Like most things it's documented by examples, and `PostJsonAsync` is demonstrated [here](http://tmenier.github.io/Flurl/), [here](http://tmenier.github.io/Flurl/fluent-http/), and [here](https://github.com/tmenier/Flurl) with an anonymous object. I don't think I've...

Better comments are in this release: https://www.nuget.org/packages/Flurl.Http/2.3.2

Rethinking this. If the thing passed to PostJsonAsync is a string, AND it parses to valid JSON, it's probably safe for Flurl to say "I know what you meant."

I'm not sure I follow. Have you looked at using the `OnError[Async]` event handler? https://flurl.dev/docs/configuration/#event-handlers