Skip to content
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

Conversation

danielkocot
Copy link

@danielkocot danielkocot commented Feb 8, 2022


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.

Copy link

@github-actions github-actions bot left a 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.

@danielkocot danielkocot changed the title added server variable object as reusable object feat: added server variable object as reusable object Feb 8, 2022
spec/asyncapi.md Outdated Show resolved Hide resolved
spec/asyncapi.md Outdated Show resolved Hide resolved
danielkocot and others added 2 commits February 9, 2022 15:42
Co-authored-by: Maciej Urbańczyk <urbanczyk.maciej.95@gmail.com>
@sonarcloud
Copy link

sonarcloud bot commented Feb 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link
Member

@magicmatatjahu magicmatatjahu left a 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

@fmvilas
Copy link
Member

fmvilas commented Feb 14, 2022

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.

@danielkocot
Copy link
Author

@fmvilas fmvilas added the 💡 Proposal (RFC 1) RFC Stage 1 (See CONTRIBUTING.md) label Feb 14, 2022
@danielkocot
Copy link
Author

Can anybody help me with the PR for the https://github.com/asyncapi/parser-js/ repo?

@magicmatatjahu
Copy link
Member

@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 serverVariables, hasServerVariables, serverVariables(name) and then write tests in the https://github.com/asyncapi/parser-js/blob/master/test/models/components_test.js file for new methods. If you will have problems please ping me :)

@danielkocot
Copy link
Author

danielkocot commented Feb 21, 2022

Last missing PR: asyncapi/parser-js#476

@derberg
Copy link
Member

derberg commented Mar 9, 2022

@danielkocot please have a look at examples. You propose serverVariables to be under components, but in examples, it is on the root.

@magicmatatjahu
Copy link
Member

@derberg Check again :) They are inside components in examples.

@derberg
Copy link
Member

derberg commented Mar 9, 2022

ah 😅 servers were also under components 😄 sorry folks 🍺

@smoya
Copy link
Member

smoya commented Mar 15, 2022

@danielkocot we have now release branches for 2.4.0. Would you mind changing the base branch to 2022-04-release ? Thanks!

EDIT: NVM! better to wait first #736 to be merged. Then I will ping you again. Thanks.

@smoya
Copy link
Member

smoya commented Mar 15, 2022

@danielkocot #736 has been merged. Would you mind changing the base branch to 2022-04-release ? Thanks!

@danielkocot danielkocot changed the base branch from master to 2022-04-release March 15, 2022 23:17
spec/asyncapi.md Outdated Show resolved Hide resolved
spec/asyncapi.md Outdated Show resolved Hide resolved
Co-authored-by: Dale Lane <dale.lane@gmail.com>
sadly it is.

Co-authored-by: Dale Lane <dale.lane@gmail.com>
Copy link
Collaborator

@dalelane dalelane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@smoya smoya mentioned this pull request Mar 21, 2022
55 tasks
@smoya
Copy link
Member

smoya commented Apr 5, 2022

@derberg can you approve the workflows so they can run? Thanks

2022-04-05 at 10 55 57

@smoya
Copy link
Member

smoya commented Apr 5, 2022

@fmvilas as per your comment, it looks OK to you. Would you mind checking again now that all PR's have been created?

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

Copy link
Member

@smoya smoya left a 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 🚀

spec/asyncapi.md Outdated Show resolved Hide resolved
Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com>
@sonarcloud
Copy link

sonarcloud bot commented Apr 6, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@smoya
Copy link
Member

smoya commented Apr 14, 2022

We still need the approval of @derberg and @fmvilas here.

@smoya
Copy link
Member

smoya commented Apr 20, 2022

@derberg @fmvilas @dalelane if you agree, please add the RFC-3 label and proceed with merging. Thanks!

@derberg derberg added 🏁 Accepted (RFC 3) RFC Stage 3 (See CONTRIBUTING.md) and removed 💡 Proposal (RFC 1) RFC Stage 1 (See CONTRIBUTING.md) labels Apr 20, 2022
@derberg
Copy link
Member

derberg commented Apr 20, 2022

done, main issue has it already too

@smoya
Copy link
Member

smoya commented Apr 21, 2022

All PR's have been merged. Proceeding with this PR.

@smoya
Copy link
Member

smoya commented Apr 21, 2022

/rtm

@asyncapi-bot asyncapi-bot merged commit 34363f6 into asyncapi:2022-04-release Apr 21, 2022
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.4.0-2022-04-release.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants