Differences Between Schema-Driven HttpApi and Router-Based API in @effect/platform
i'm trying to understand the difference in @effect/platform's Schema driven HttpApi and the router based api.
With HttpApi, are you unable to set cookies? Is that too low level for the abstraction? If you just return an HttpServerResponse from the handler, then you get an
I'm trying to get the best of both worlds, i need to control cookies (very limited) on the server responses but i'd love the swagger functionality and schema type safety
With HttpApi, are you unable to set cookies? Is that too low level for the abstraction? If you just return an HttpServerResponse from the handler, then you get an
Effect<HttpServerResponse...>I'm trying to get the best of both worlds, i need to control cookies (very limited) on the server responses but i'd love the swagger functionality and schema type safety
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
