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: add Solace bindings to the list of supported bindings in the spec. #666

Merged

Conversation

damaru-inc
Copy link
Contributor

@damaru-inc damaru-inc commented Dec 6, 2021


title: "Add Solace bindings to the list of supported bindings in the spec."

This is a request to add the Solace bindings to the lists of bindings in the spec.

The PR for the json schema repo corresponding to this PR is here: asyncapi/spec-json-schemas#136

@jessemenning
Copy link

Looks good to me, excited to have Solace join the bindings.

Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

@MichaelDavisSolace please also update the sections I shared in below screen shots

(1)
Screenshot 2021-12-21 at 16 52 27
(2)
Screenshot 2021-12-21 at 16 52 38

@fmvilas IMHO we can move it to Draft stage as PR for schema is also there. There are some fixes needed for this PR but this is why it is stage 2 not 3

@sonarcloud
Copy link

sonarcloud bot commented Dec 21, 2021

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

@fmvilas
Copy link
Member

fmvilas commented Dec 23, 2021

Yeah, I think this can be marked as Draft already. @MichaelDavisSolace I think the next step would be to get the JSON Schema version into the JS Parser and we'd be done. In the parser, you can point to your branch temporarily so it can be tested.

@fmvilas fmvilas added the 📄 Draft (RFC 2) RFC Stage 2 (See CONTRIBUTING.md) label Dec 23, 2021
@damaru-inc
Copy link
Contributor Author

Yeah, I think this can be marked as Draft already. @MichaelDavisSolace I think the next step would be to get the JSON Schema version into the JS Parser and we'd be done. In the parser, you can point to your branch temporarily so it can be tested.

Okay, will do.

@damaru-inc
Copy link
Contributor Author

I see Dale Lane is the one who got the 2.3.0 schema into the spec-json-schemas repo. Does that mean that he'll be the one to update parser-js?

@derberg derberg added 🏁 Accepted (RFC 3) RFC Stage 3 (See CONTRIBUTING.md) do-not-merge and removed 📄 Draft (RFC 2) RFC Stage 2 (See CONTRIBUTING.md) labels Jan 3, 2022
Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

@fmvilas I approved this one and promoted to accepted

Imho asyncapi/spec-json-schemas#143 is enough for now and agree with one of the comments Michael did in Slack that in case of this feature, where there is just small change in the schema, it doesn't make sense to open up a PR before asyncapi/spec-json-schemas#143 is actually merged and the release candidate is ready.

So @fmvilas once you approve this one and release it, then release PR for JSON Schema, please just open a bump PR in the Parser to the release branch...or just merge together with asyncapi/parser-js#430 and @smoya will bump it

Copy link
Member

@fmvilas fmvilas left a comment

Choose a reason for hiding this comment

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

Yeah, makes sense to me. Approving 👍

@fmvilas
Copy link
Member

fmvilas commented Jan 3, 2022

/rtm

@asyncapi-bot asyncapi-bot merged commit 88abbe0 into asyncapi:2022-01-release Jan 3, 2022
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.3.0-2022-01-release.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@damaru-inc damaru-inc deleted the mdavis/add-solace-bindings branch January 3, 2022 16:57
Polo2 added a commit to Polo2/bindings that referenced this pull request May 20, 2022
Solace Binding Protocal has been included with release 2.3.0 of AsyncAPI,
with:
- asyncapi/spec@88abbe0
- asyncapi/spec#666

Thus, specification example should indicate at least this version.

---

Noticed by working on Solace Protocol support on https://bump.sh
Polo2 added a commit to Polo2/bindings that referenced this pull request May 20, 2022
Solace Binding Protocol has been included with release 2.3.0 of AsyncAPI,
with:
- asyncapi/spec@88abbe0
- asyncapi/spec#666

Thus, specification example should indicate at least this version.

---

Noticed by working on Solace Protocol support on https://bump.sh
Polo2 added a commit to Polo2/bindings that referenced this pull request May 24, 2022
Solace Binding Protocol has been included with release 2.3.0 of AsyncAPI,
with:
- asyncapi/spec@88abbe0
- asyncapi/spec#666

Thus, specification example should indicate at least this version.

While here, let's favor last released version 2.4.0, as suggested by @fmvilas

---

Noticed by working on Solace Protocol support on https://bump.sh/asyncapi
Polo2 added a commit to Polo2/bindings that referenced this pull request Jun 1, 2022
Solace Binding Protocol has been included with release 2.3.0 of AsyncAPI,
with:
- asyncapi/spec@88abbe0
- asyncapi/spec#666

Thus, specification example should indicate at least this version.

While here, let's favor last released version 2.4.0, as suggested by @fmvilas

---

Noticed by working on Solace Protocol support on https://bump.sh/asyncapi
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.

6 participants