Migrations
To v9 (Breaking Changes)
http...Builders: There is now only a singlehttpbuilder, that is equivalent to the formerhttpLazybuilder. To achieve the behaviour of the removed builders, please use:httpLazy->http { ... }http->http { ... } |> Request.sendhttpAsync->http { ... } |> Request.sendAsynchttpLazyAsync->http { ... } |> Request.toAsynchttpMessage->http { ... } |> Request.toMessage- see also: https://github.com/fsprojects/FsHttp/blob/master/src/Tests/BuildersAndSignatures.fs
- Renamed type
LazyHttpBuilder->HttpBuilder - Renamed
Request.buildAsync->Request.toAsync - Removed
sendandsendAsyncbuilder methods - Changed request and response printing (mostly used in FSI)
- Printing related custom operations change in names and behaviour
Dsl/DslCEnamespaces: There is no need for distinction of both namespaces. It is now sufficient toopen FsHttponly.- The
HttpBuilder<'context>is replaced byIBuilder<'self>, so that the CE methods work directly on theHeaderContext,BodyContext, andMultipartContextdirectly. This simplifies things like mixing Dsl and DslCE, pre-configuring and chaining requests. - The global configuration is now in the
FsHttp.GlobalConfigmodule. TheConfigmodule is only for functions on request contexts. - QueryParams is
(string * obj) listnow - Use of System.Text.Json as a standard JSON library and created separate Newtonsoft and FSharp.Data JSON packages.
- Dropped support for .Net Standard 2.0
- Smaller breaking changes
FsHttp