Nabil Abdel-Hafeez
Nabil Abdel-Hafeez
Currently we can handover docs explicitly in the in/out methods of the Endpoint API or use `??` on a content codec to add docs to the type while generating OpenAPI....
Currently this code in `EndpointClient` ```scala if (response.status.isSuccess) { endpoint.output.decodeResponse(response).orDie } else { //use error codec } ``` forces the error codec to be used for all status codes that...
@jdegoes I did not follow the plan as described in the ticket due to learnings while implementing it. > If the user does not handle the error explicitly, then we...
Both [smithy](https://smithy.io/1.0/spec/core/documentation-traits.html#tags-trait) and [OpenAPI](https://swagger.io/docs/specification/grouping-operations-with-tags/) offer tagging for endpoints. The Endpoint API should have a concept of tagging endpoints. And they should be included in generated OpenAPI objects
Currently we only return a http 400, if the endpoint API can't decode the request. That is not very helpful to the user/dev. They can't know what exactly went wrong....
No explicit schema definition in a companion object of a type `B` that is used by a type `A`, that derives its schema, leads to the schema of `B` being...
This PR is not good to go, but shows that I found a way how to provide a context to multiple routes without any more explicit typing or extremely strange...
@jdegoes I think the brotli4j dependency is okay. It would go to the netty backend module once we split zio-http core and netty backend. fixes #2646 /claim #2646
Currently, we can require the authorization header in the endpoint API, but we do not know, if this is for example Basic Auth or Bearer Auth. This makes it impossible...
Currently we have `Route.handleErrorCause(f: Cause[Err] => Response)` that gives access to the `Err` and it's cause. We would like to have a variant, that also let's one access (parts of)...