Create HttpApp and HttpRoutes Defaults for Server Middleware

Server Middleware that is defined on Http[F, G] can sometimes be hard to reason about for folks who are trying to get a handle on the Http process. Rather than forcing individuals to learn Kleisli Composition, and FunctionK, we can create function which summon that middleware on HttpRoutes, or HttpApp respectively with OptionT.liftK and FunctionK.id. As its just a default argument being plugged in, but will make the middleware far more approachable without losing any of the composition the get Http types give us.

So each middleware would get on that take and HttpRoutes[F], and an HttpApp[F], preferably names def httpRoutes and def httpApp

[rossabaker]

Apologies, I’ve been drowning in notifications.

• Agreed on MonoidK.
• Agreed with putting constructors on the builders where there are builders.
• The object seems reasonable for named constructors. It’s consistent with the majority if we think of them all as having that, with an implicit “apply”.

So, yeah, 👍.

[bplommer]

In https://github.com/http4s/http4s/pull/6629 I took a different approach of adding a Lift type class that provides the FunctionK instance. That pull request also deprecates the httpApp/httpRoutes constructors - do people feel strongly about having httpApp and httpRoutes constructors in addition?