zio-http
zio-http copied to clipboard
zio
A next-generation Scala framework for building scalable, correct, and efficient HTTP clients and servers
OpenAPI supports such limitations and it also seems fitting for our API.
**Is your feature request related to a problem? Please describe.** Currently, `PathCodec#/` requires the `Routes` passed to it to have the errors handled and/or mapped to `Response`. This limits where...
**Is your feature request related to a problem? Please describe.** I need to be able to return JSON from APIs where empty collections are serialized as `"myList": []` instead of...
**Describe the bug** With parameterized case class used as endpoint's output, Open API documentation generator crashes. **To Reproduce** Steps to reproduce the behaviour: 1. Run the following code: ``` //>...
For a field of type Map[String, List[String]] (or List of anything for that matter), the OpenAPI generator fails Run this program to reproduce: ``` import zio.http.endpoint.openapi.JsonSchema import zio.http.endpoint.openapi.JsonSchema.SchemaStyle import zio.schema.*...
**Is your feature request related to a problem? Please describe.** Currently, `zio-http` provides 2 config options for `RequestStreaming`: 1. `Disabled` (with a maximum number of bytes that the request can...
Assume I have the following ZIO HTTP App: ```scala object MainApp extends ZIOAppDefault { def run = Server.serve( Routes( Method.GET / "hello" -> handler(Response.ok), ), ).provide( Server.live, ZLayer.fromZIO(ZIO.config(Server.Config.config)).debug) ) }...
Hi! Would it be possible to add support for accessing Env in e.g. Routes.handleErrorRequestCauseZIO(f: (Request, Cause[Err]) => ZIO[Any, Nothing, Response]): Route[Env, Nothing] so it becomes Routes.handleErrorRequestCauseZIO(f: (Request, Cause[Err]) => ZIO[Env,...
**Describe the bug** When using a websocket, sending a message to early as the server can cause problems in netty. The initial connection is established with no signs of problems...
