The Scala HTTP client you always wanted!
Some modules of sttp 3.8.16 have switched to Cats Effect 3.5.1, which changes the way Async.async, Async.async_, and Async.fromFuture behave around cancellation. If your project relies on Cats Effect 3, read CE release notes and make sure your usages of mentioned methods are aligned.
This is the first milestone release for the upcoming sttp 4. The focus of this release is to simplify the types used by sttp, improve type inference and error reporting, while keeping the same API.
Hence the good news: if you are using sttp 3, your code should work with minimal changes. These should concern mainly the types, and code organization (package names). If you'd like to help us and try out this release, please do - and report anything that has been unexpectedly broken.
sttp 4 uses a new organization (com.softwaremill.sttp.client4) and package name (sttp.client4), so you can safely use both v3 and v4 in a single codebase.
If you'd like to test the new release, check out the updated quickstart documentation page.
And finally, for feedback regarding this release, or suggestions on what to improve in further milestone releases (NOW is the best time to let us know what you found irritating or broken in sttp v3), please let us know on the community forum. Thank you!
Thanks to @adpi2 for the PR transforming how we define requests & backends.
RequestT, introduce PartialRequest, Request, StreamRequest, WebSocketRequest, WebSocketStreamRequest
SttpBackend to GenericBackend, introduce subtypes: Backend, StreamBackend, SyncBackend etc.SttpBackendOptions to BackendOptions
Backend.responseMonad to Backend.monad
request.send(backend) is now the only preferred method of sending a requestSimpleHttpClient
HttpClientBackend to a dedicated package, introduce DefaultSyncBackend and DefaultFutureBackend
Drops support for 2.11 + JS/Native