Open jdegoes opened 1 month ago
/bounty $1500
/attempt #2888
with your implementation plan/claim #2888
in the PR body to claim the bountyThank you for contributing to zio/zio-http!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🔴 @987Nabil | Jun 6, 2024, 7:04:48 PM | #2947 |
🟢 @promisingcoder | Jul 2, 2024, 10:05:25 PM | WIP |
/attempt
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@987Nabil | 35 ZIO bounties + 1 bounty from 1 project |
Scala |
Cancel attempt |
@987Nabil: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏
The bounty is up for grabs! Everyone is welcome to /attempt #2888
🙌
/attempt
Will be streaming the impl. tomorrow or on the weekend
/attempt #2888
💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward.
Right now, we cannot enforce that endpoint middleware is actually implemented (it's a very complicated problem that cannot be solved in time for release). Simultaneously, we cannot document security requirements of endpoints.
To fix this issue, we should instead use a
sealed trait AuthType
, or similar, which is placed intoEndpoint
. Based on this, we can generate OpenAPI documentation, as well as potentially even leverage this information in the automatic HTTP client.Note that endpoint auth type would still be a type parameter, albeit constrained (Z <: AuthType). The reason is to statically retain the type members inside the
AuthType
value, so they can be used by client and server.This requires more R&D but should address all of the issues with endpoint middleware that we have, currently. The question is, can we do it in time? 😄