-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Properly support content type headers in zio.http.api #1506
Comments
In particular, since ZIO Schema supports several different protocols, including gRPC, endpoints should properly support those protocols, based on |
/bounty $250 |
💎 $250 bounty created by jdegoes
|
@jdegoes the only protocol besides json, that zio-schema supports and does have an official mime-type is thrift. |
@987Nabil I would rather not make it configurable and choose based solely on |
|
@jdegoes but which accept values? There is no standard. |
Let's say that is okay for protobuf and the case you described. What about the other formats? |
/attempt #1506 |
💡 @987Nabil submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
🎉🎈 @987Nabil has been awarded $250! 🎈🎊 |
Is your feature request related to a problem? Please describe.
Currently,
EndpointClient
andEndpointServer
inzio.http.api.internal
do not perform an adequate job supporting and respecting content type headers.Describe the solution you'd like
Modify the client and server to respect and generate the appropriate content type headers, and enhance the architecture to support any one of the protocols supported by ZIO Schema, which powers the current JSON support.
Describe alternatives you've considered
None.
Additional context
See
/src/main/scala/zio/http/api/internal/
EndpointClient.scala
andEndpointServer.scala
.The text was updated successfully, but these errors were encountered: