-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
fix: incorrect rendering of security schemas #995
fix: incorrect rendering of security schemas #995
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @derberg Do you wanna add something?
@RobinTail due to some refactor from #996 you need to solve merge conflicts. Sorry about that. |
Quality Gate passedIssues Measures |
@derberg && @magicmatatjahu , |
Thanks @RobinTail /rtm |
🎉 This PR is included in version 1.4.10 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes #993
Incorrect rendering of security schemas in AsyncAPI 3.0, by reference and inline.
See asyncapi/studio#1066
Changes proposed in this pull request:
security
property supplied toSecurity
component seems to be enough to fix all issues:Perhaps I didn't understand something, but without all those complications it seem to work well on all cases and the tests are passing. Anyway, consider it a proposal, feel free to make or request changes.
Related issue(s)
asyncapi/studio#1066