Todd Menier

I've [heard](https://github.com/tmenier/Flurl/issues/349#issuecomment-557545982) this request before and there's definitely interest in it, but I agree with all the drawbacks as well. Aside from platform support, I'm worried I'd break a lot...

@mincasoft Yes, you can definitely swap out Newtonsoft for System.Text.Json today: https://flurl.dev/docs/configuration/#serializers For most people though, I'm pretty sure the motivation is to eliminate the Newtonsoft dependency and/or reduce the...

I'm confident this will happen in future major release, but it isn't gonna make the 3.0 cut. I could see an optional `Flurl.Http.Newtonsoft` package or something for those who want...

@panoukos41 Thanks, good to know that works. Hopefully others who want to use System.Text.Json today will find that useful.

@benwmills You can also [swap out](https://flurl.dev/docs/configuration/#serializers) the (default) Newtonsoft serializer for [this one](https://github.com/tmenier/Flurl/issues/517#issuecomment-821541278), which I think is a better option in your case than any of those you mentioned.

My plan is to swap out Newtonsoft for System.Text.Json and release as 4.0-pre1 relatively soon. It should be considered reasonably stable since it will consist of virtually no other changes...

Also adding a `net6.0` target. From what I can tell, no version of .NET Standard supports System.Text.Json and therefore Flurl would always download the separate NuGet package, which probably wouldn't...

@Hawxy > Anyone using Blazor is using at minimum .NET Core 3.1 which already includes S.T.J so that isn't a problem. The problem, and please correct me if this is...

I've hit a bump in the road with this. Deserializing to a `dynamic` is a [first-class feature](https://flurl.dev/docs/fluent-http/) of Flurl but isn't supported with STJ. Comment [here](https://github.com/dotnet/runtime/issues/29690#issuecomment-686651689) best describes what I'm...

Ok, you asked for it, dynamic returning methods in Flurl are getting the 🪓! #699