You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some general refactoring aimed at simplifying some core Flurl.Http classes and interfaces resulted in a few breaking changes. This issue is catch-all to make sure those get documented.
FlurlClient.Settings and FlurlRequest.Settings container objects are read-only.
FlurlClient.HttpMessageHandler removed.
FlurlCall.RedirectedFrom moved to IFlurlRequest.
FlurlResponse ctor takes a FlurlCall instead of an HttpResponseMessage.
FlurlRequest.Client is no longer instantiated on demand by just referencing the property. If it hasn't been set explicitly, or (more common) by calling FlurlClient.Request, it will remain null until the request is sent.
The text was updated successfully, but these errors were encountered:
Some general refactoring aimed at simplifying some core Flurl.Http classes and interfaces resulted in a few breaking changes. This issue is catch-all to make sure those get documented.
FlurlClient.Settings
andFlurlRequest.Settings
container objects are read-only.FlurlClient.HttpMessageHandler
removed.FlurlCall.RedirectedFrom
moved to IFlurlRequest.FlurlResponse
ctor takes aFlurlCall
instead of anHttpResponseMessage
.FlurlRequest.Client
is no longer instantiated on demand by just referencing the property. If it hasn't been set explicitly, or (more common) by callingFlurlClient.Request
, it will remain null until the request is sent.The text was updated successfully, but these errors were encountered: