-
Notifications
You must be signed in to change notification settings - Fork 378
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
The securityScheme in the OpenAPI specification is being parsed incorrectly #2813
Labels
Comments
/bounty $75 |
💎 $75 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 9, 2024
987Nabil
added a commit
to 987Nabil/zio-http
that referenced
this issue
Jun 9, 2024
987Nabil
added a commit
to 987Nabil/zio-http
that referenced
this issue
Jun 9, 2024
987Nabil
added a commit
to 987Nabil/zio-http
that referenced
this issue
Jun 9, 2024
jdegoes
pushed a commit
that referenced
this issue
Jun 11, 2024
🎉🎈 @987Nabil has been awarded $75! 🎈🎊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hi, I am trying to generate the openApi specification using zio-http 3.0.0-RC6
But there seems to be an issue with the securityScheme, it’s not parsed correctly.
To Reproduce
This is the code:
And this is how it is parsed
Expected behaviour
The expected format of the securitySchemes is :
The text was updated successfully, but these errors were encountered: