`Http4sMatchers` isn't parameterised on Effect type
See original GitHub issueI’ve upgraded to 0.18.0-M1 but Http4sMatchers
isn’t parametrised on the effect type, so matchers like haveStatus
don’t work if I’m using something other than cats.effect.IO
(eg: cats.Id
)
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
why is there a type parameter IO in Request as in http4s ...
There's a type parameter IO in Request as in http4s Request[IO] . Why is it necessary, what do we have as an effect...
Read more >proposal: spec: allow type parameters in methods · Issue ...
According to the Type parameters proposal, it is not allowed to define type parameters in methods. This limitation prevents to define ...
Read more >The http4s DSL
In the following we use cats.effect.IO as the effect type F . val service = HttpService[IO] { case _ => IO(Response(Status.
Read more >Azure Policy pattern: parameters - Microsoft Learn
A common way to make policy definitions reusable is to parameterize the effect itself. This example uses a single parameter, effect.
Read more >Parameterized Queries · doobie - tpolecat
When setting parameters in the high-level API, we require an instance of Write[A] for the input type. It is not immediately obvious when...
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
Happy to put in a PR if that will help
I haven’t, I apologize. Feel free to take it!