Removal of `ResponseOps` breaks Rho's `Result` - Http4s `Response` parity.
See original GitHub issueThis commit b54af3a12b5f7b838d9346171a902224411a13d1 in PR #2234 breaks Rho here. Rho was using the ResponseOps
trait to keep the the signature of the Result and response types the same. Unfortunately without it Rho will need to manually keep pace. Could we possibly bring back the ResponseOps
? Is there some other mechanism we can use to have Rho keep pace?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Changelog - http4s
Spring cleaning: Remove unneeded temporal constraints and make some cosmetic changes by @FrancescoSerra in https://github.com/http4s/http4s/pull/6491 ...
Read more >The http4s DSL
The code associated with the first matching case is used to generate a F[Response[F]] . The simplest case statement matches all requests without ......
Read more >org.http4s.Response
Set an empty entity body on this message, and remove all payload headers that make no sense with an empty body.
Read more >Middleware - http4s
A middleware is a wrapper around a service that provides a means of manipulating the Request sent to service, and/or the Response returned...
Read more >The http4s DSL
The central concept of http4s-dsl is pattern matching. An HttpRoutes[F] is declared as a simple series of case statements. Each case statement attempts...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s what I think we will do for now. I’ll define typeclass instances for Response in Rho for now, with the goal of (at least making an attempt) to moving that into the Core.
This moved to rho for now, and we can look into removing that from rho when the typeclass happens.