Support custom encoding and decoding for Endpoint parameters (in, out, error)

[jdegoes]

Support custom encoding and decoding for Endpoint parameters (in, out, error)

[jdegoes]

/bounty $500

[algora-pbc]

💎 $500 bounty created by ZIO
🙋 If you start working on this, comment /attempt #2625 along with your implementation plan
👉 To claim this bounty, submit a pull request that includes the text /claim #2625 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to zio/zio-http!

👉 Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟡 @987Nabil	Jan 17, 2024, 2:02:10 PM	#2655

[guersam]

@jdegoes Could you elaborate a use case enabled by HttpContentCodec that isn't supported by Schema? It will be helpful for implementation.

[987Nabil]

/attempt #2625

[987Nabil]

@jdegoes we still need to put the Schema somewhere. Else we lose the ability to use it for meta analysis (OpenAPI generation for example). I would suggest as an additional field of HttpContentCodec

[algora-pbc]

@987Nabil: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏

[algora-pbc]

💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[algora-pbc]

🎉🎈 @987Nabil has been awarded $500! 🎈🎊

• Share on socials
• Give feedback