Ben Plommer
Ben Plommer
The current implementation seems to be incorrect with respect to case-sensitivity: According to [RFC 7231, section 3.1.1.1](https://httpwg.org/specs/rfc7231.html#media.type) the main type, subtype, and parameter names are case-insensitive, but as currently implemented...
Depends on #5229. Closes https://github.com/http4s/http4s/issues/3114. It's a big diff so here's a breakdown: - 1672e6dbb23d40a3d1af22d060be3c513450b20f is the core change. - 2d140833d81ee6e362302f08e336df5478f0611a removes no-longer-needed type arguments and annotations from production code;...
Also made `Content-Length` a value class, so it shouldn't be any more costly.
Lifting information in `Status` to type level in a backwards-compatible way is surprisingly straightforward. Trying to preserve that information in `Response` leads to a world of variance-related hurt. `ResponseBuilder` a...
Quite a few headers don't yet have typed models. The following are the unmodelled headers that have their own page on [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), excluding those marked as deprecated. - [ ]...
I suggest adding a linter that warns about discarded values regardless of type, for use with pure functional code. This is in a sense a generalisation of scala's built-in "discarded...
This requires `Trace` to expose a type member representing the type of `Span` it uses, which is a bit nasty, but it allows some nice extra functionality. The sorting example...