14 replies

Feedback on Migrating from `effect-http` to `HttpApiBuilder`

I don't want this to sound like a hate so try to take it like an honest criticism from a fan of this project but so far I am very unimpressed when trying to migrate from

effect-http

effect-http

to new HttpApiBuilder. The API of RouterBuilder was very straightforward and very easy to navigate when I wanted to add middleware and routes that weren't part of the API - because it simply built a Router instance which could be mapped, mounted or joined with other router. HttpApiBuilder treats Api like a completely separate thing from HtpRouter which is kinda frustrating.

Feedback on Migrating from `effect-http` to `HttpApiBuilder`

Similar Threads

Feedback on Migrating from `effect-http` to `HttpApiBuilder`

Similar Threads

Similar Threads

Similar Threads