-
Notifications
You must be signed in to change notification settings - Fork 412
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
Use @description
zio-schema annotation at types for generating OpenAPI docs
#2722
Comments
@fernanluyano this is related, but not the same. The error you describe comes due to the fact that the field is optional and therefor left out when serialising the open API. Is should be non optional with a default value. This is, that we want to have a different source for the docs. And this is not a bug. |
/bounty $150 |
💎 $150 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-http! Add a bounty • Share on socials
|
/attempt #2722
|
is this issue still open @987Nabil ? |
💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
@mobley-trent Hey 👋 Sorry, I actually just opened a PR for this. Should have written here something first I guess 😅 |
🎉🎈 @987Nabil has been awarded $150! 🎈🎊 |
Currently we can handover docs explicitly in the in/out methods of the Endpoint API or use
??
on a content codec to add docs to the type while generating OpenAPI. We should also respect the@description
annotation of zio-schema for the type, if it exists.This is already working for fields, but not for top-level types.
The text was updated successfully, but these errors were encountered: