-
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
Decide using Endpoint codec in client based on status code #2727
Labels
Comments
/bounty $150 |
💎 $150 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-http! Add a bounty • Share on socials
|
💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
987Nabil
added a commit
to 987Nabil/zio-http
that referenced
this issue
Jun 22, 2024
jdegoes
pushed a commit
that referenced
this issue
Jun 22, 2024
🎉🎈 @987Nabil has been awarded $150! 🎈🎊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently this code in
EndpointClient
forces the error codec to be used for all status codes that are not 2xx/3xx.
This is an issue, since I as a user cannot decide that for example a 2xx is an error or a 4xx is not (means goes to
E
orA
of the resulting ZIO).We should choose the codec purely based on the mapping from returned status code to the codec with that status code.
The text was updated successfully, but these errors were encountered: