StableReq - a fork of Req with API stabilized at v0.7.4

News Announcing
,
1

StableReq

Its Req, but with API stabilized at 0.7.4.

What?

It is a fork of Req project, but with API locked to 0.7.4. I intend to keep this project synced with the upstream as much as I can.

Why?

  1. I’ve had two incidents in my production related to updating Req. Req frequently (almost every minor release) introduces breaking changes and some of them are silently introducing bugs. No deprecations, no warnings, just incidents.

  2. I took a look at the Req 0.8.0-rc changelog and it had a lot of breaking changes. I quickly understood that I don’t want to refactor my code, so here we are.

  3. I’ve been waiting for Req 1.0.0, but I don’t see it coming in any near future and I can’t build my projects on the promises

What about incompatible changes?

If an incompatible breaking change is introduced, 0.7.4 compatibility will take priority. Most of these incompatible changes are just switching of the defaults, or just changes in cosmetics, so no essential features will be lost.

3 Likes
2

Cool, why not just use httpc instead?

Then you also don’t have to maintain that other then your application code.