-
Notifications
You must be signed in to change notification settings - Fork 416
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
Serving Individual Routes That are Ready to be Served #2805
Labels
Comments
/bounty $50 |
💎 $50 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. |
jdegoes
pushed a commit
that referenced
this issue
Jun 7, 2024
🎉🎈 @987Nabil has been awarded $50! 🎈🎊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After removing
HttpApp
, another thing that can make APIs simpler is to have aServer
that can serve variable length arguments of individual routes. like this:The
Routes
is useful to take the last step in making the routes ready to be served, such as handling errors, applying middlewares, sandbox, etc. However, sometimes, we do not need this step, and our routes are ready to be served and all of their error are handled by converting toResponse.
It can reduce one level of indirection on use-cases like this:
The text was updated successfully, but these errors were encountered: