-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
feat: added server variable object as reusable object #717
feat: added server variable object as reusable object #717
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.
Co-authored-by: Maciej Urbańczyk <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
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.
For me it looks good 🚀 We have first feature to 2.4.0
!
I'm not a maintainer of that repo, so I cannot accept it 😅 cc @derberg @fmvilas
You should be also interest @smoya @jonaslagoni
LGTM so far 👍 The only thing I'm missing now is the PRs on the https://github.com/asyncapi/spec-json-schemas and https://github.com/asyncapi/parser-js/ repos. |
Can anybody help me with the PR for the https://github.com/asyncapi/parser-js/ repo? |
@danielkocot Sure! You should write needed method for new field in this class https://github.com/asyncapi/parser-js/blob/master/lib/models/components.js like |
Last missing PR: asyncapi/parser-js#476 |
@danielkocot please have a look at examples. You propose |
@derberg Check again :) They are inside |
ah 😅 servers were also under components 😄 sorry folks 🍺 |
EDIT: NVM! better to wait first #736 to be merged. Then I will ping you again. Thanks. |
@danielkocot #736 has been merged. Would you mind changing the base branch to |
Co-authored-by: Dale Lane <[email protected]>
sadly it is. Co-authored-by: Dale Lane <[email protected]>
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 👍
@derberg can you approve the workflows so they can run? Thanks |
@fmvilas as per your comment, it looks OK to you. Would you mind checking again now that all PR's have been created? |
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.
@danielkocot there is only one little thing to fix here and we will be most probably ready to merge it soon 🚀
Co-authored-by: Sergio Moya <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
done, main issue has it already too |
All PR's have been merged. Proceeding with this PR. |
/rtm |
🎉 This PR is included in version 2.4.0-2022-04-release.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
title: "Server Variable Object as reusable object"
Related issue(s):
#707
The PR targets to have Server Variable Objects as reusable objects within the Component Object.