Flurl: 3.0 Planning / Announcements

[tmenier]

This issue will serve as a hub to discuss and communicate the overall vision/direction of Flurl and Flurl.Http 3.0. The only thing to announce so far is that many ideas, mostly from the community, are on the table and I'm looking for help prioritizing them. The best way to help is to vote for the feature(s) you most want to see here: [Survey now closed, results posted below.]

Also note that the 3.0 label I've added to many issues should be taken with a grain of salt. I started using that as way to classify issues that _might_ make good candidates for 3.0, but it's no guarantee they'll get in, nor is it certain that open issues _not_ labeled 3.0 _won't_ get in. I'll try to get a better system in place soon.

[tmenier]

Survey results:

Flurl 3.0 Survey Results.pdf

[tmenier]

I haven't been updating this issue as promised. Maybe it's a good place to highlight what's _new_ in each prerelease? Full summary of what's been (pre)released is kept up to date in the release notes, and all 3.0 issues are labeled as such.

Here are the main things just release in 3.0-pre4:

• Cookies overhaul: #506
• Redirects overhaul: #500
• New collection type for headers (breaking): #541
• Some new test assertions: #508

[tmenier]

Just released in 3.0-pre5:

• New collection type for Url.QueryParams (#555)
• Default HttpClient caching strategy based on host, scheme, and port, rather than just host (#550)
• Minor changes/enhancements to HttpCallAssertion (#483)
• Parameterless ctor for Url (#518)
• Providing a body for PostAsync, PutAsync, and PatchAsync now optional (#515)
• For multipart requests, Content-Type header for text parts allowed but not defaulted (#452)
• Minor changes to CapturedStringContent constructors (#452)
• Source Link support added (thx @gitfool #513)
• Dropping support for older platforms (#544)
• Culture-neutral string comparisons throughout library (#485)
• Fixed PlatformNotSupportedException error reported on some WASM-based platforms (#543)
• HttpRequestMessage.GetHeaderValue and HttpResponseMessage.GetHeaderValue extension methods removed (#553)

As usual, cumulative release notes for 3.0 are here.

[tmenier]

Just released in 3.0-pre6:

• Bugfix: header names should be case-insensitive
• Bugfix: algorithm for determining when to send cookies without explicit Path attribute was incorrect in some cases
  (#560)