Adam Warski

Last call to take a look at a proposal to overhaul the type hierarchy of sttp's `Request`!

Is the current approach a hurdle for newcomers? Do we solve the right problem, as does it justify a new major release (& migration)?

Let us know :)

https://github.com/softwaremill/sttp/pull/1703

Especially if you started using #Scala or #sttp recently - your feedback would be most welcome. Thank you!

[Proposal] Add type hierarchy of requests and backends by adpi2 · Pull Request #1703 · softwaremill/sttp

Following the discussion in #1607, I started experimenting with sttp, to see if it was possible to get a more user-friendly API while preserving the full power and flexibility. I did not try to mai...

GitHub
Feb 1, 2023 at 10:18amWeb
Show threadMichał PawlikFeb 1, 2023
@adamwarski Do you have any binary release version to play around with?
Show threadAdam WarskiFeb 1, 2023
@majkp No, not yet, we'd need to merge this into a branch & release
Show threadMichał PawlikFeb 1, 2023
@adamwarski thanks! I'll try to build the fork and publish it locally then
Show threadMarcin Szałomski 🌀Feb 4, 2023
@adamwarski I don't know whether the current approach hurdle newcomers, however regarding solving the right problem, I think it is. I mean the following solution: "no RequestT[Identity, T, Any] or SttpBackend[Identity, Any] exposed to the user anymore". We found it noisy and created type aliases to hide a bit of it. Also, the `Any` generated a lot of Wartremover noise we couldn't hide if not suppressing the warnings. Now it won't be a problem anymore. Such improvements make the change proposal very promising.
Show threadAdam WarskiFeb 4, 2023
@baldram thanks for the feedback! :)