http4s/http4s-finagle

Http4s on Finagle Server or Client

Http4s Finagle

📖 Document

🔍 API

🔧 Test

http4s-finagle's Issues

Versioning scheme

The versioning scheme is clever, but it's not the semantic versioning seen in most Scala libraries. I'm wondering how it plays with things like eviction notices, Scala Steward labelling, etc. And more importantly, what happens if you ever want to make a breaking change outside http4s and finagle's own cycles?

This is the first satellite repo that ties together two major, independent dependencies. (rho is its own thing, and jdk-http-client integrates something in the JDK). It's a problem we'll be having a lot if we start to split up http4s/http4s. It would be good to have a consistent solution, so I'm interested to see how this scheme plays out in practice.