Milan Suk

For the record, some time ago, I included the `Handler` module which enables a better modularisation. See the [readme](https://github.com/sukovanej/effect-http?tab=readme-ov-file#scaling-up)

Yeah, I already thought about it. That holds for the middlewares like CORS in the codebase as well. Now that I see an outside interest in that, I might actually...

Hey, done within the latest release. Readme, examples and probably some combinators enabling easy integration with a /platform are missing tho.

We discussed potential merge of this lib to the official effect monorepo. Independently of how that'll turn out, we talked with fubhy about the separation of packages and the result...

Could you please send a snippet or push this somewhere? On the type level, the error channel of a handler function is not constrained. The `RouterBuilder.handle` only excludes `ServerError` from...

I see. Yeah, the problem is the query parameters are first parsed onto a javascript object (by the `@effect/platform`) and only then they are passed to the schema decoder. The...

Should be solved by the new `QuerySchema` module.

Hey, I agree the error responses are handled poorly right now. The most problematic traits I currently see: - the missing type-safety and validation on the client side - what...

Hey, for non-json responses, you'd currently need to use `RouterBuilder.handleRaw` and construct the response yourself. ```ts import * as Http from "@effect/platform/HttpServer"; ... export const app = RouterBuilder.make(api).pipe( RouterBuilder.handleRaw( "root",...

And I'll fix the example, thanks for letting me know 👍