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

docs: clarify the meaning of components #803

Merged
merged 2 commits into from
Jul 25, 2022

Conversation

fmvilas
Copy link
Member

@fmvilas fmvilas commented Jun 8, 2022

This PR clarifies the meaning of the Components Object and, more importantly, the meaning of everything outside the Components Object.

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 Jul 5, 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 Jul 7, 2022

@fmvilas Is this really introducing a breaking change? I'm not very sure and I would say it doesn't. If you think it doesn't, would you like to include this into 2.4.1 release? This is ready to be merged: #776 but we could pack both PR's into the same release.

@fmvilas
Copy link
Member Author

fmvilas commented Jul 7, 2022

I don't see the need to rush on this PR so I prefer to wait for 3.0.0 to be honest.

@jonaslagoni jonaslagoni mentioned this pull request Jul 18, 2022
@jonaslagoni
Copy link
Sponsor Member

What can we do to move this forward, is it only reviews we need @fmvilas ? 🙂

@fmvilas
Copy link
Member Author

fmvilas commented Jul 18, 2022

Yup, reviews are needed. Not just from @dalelane and @derberg but also y'all.

@fmvilas
Copy link
Member Author

fmvilas commented Jul 25, 2022

/rtm

@asyncapi-bot asyncapi-bot merged commit caf8c75 into asyncapi:next-major-spec Jul 25, 2022
@fmvilas fmvilas deleted the clarify-components branch July 25, 2022 16:02
fmvilas added a commit that referenced this pull request Sep 22, 2022
@@ -157,7 +159,7 @@ Field Name | Type | Description
<a name="A2SServers"></a>servers | [Servers Object](#serversObject) | Provides connection details of servers.
<a name="A2SDefaultContentType"></a>defaultContentType | [Default Content Type](#defaultContentTypeString) | Default content type to use when encoding/decoding a message's payload.
<a name="A2SChannels"></a>channels | [Channels Object](#channelsObject) | **Required** The available channels and messages for the API.
<a name="A2SComponents"></a>components | [Components Object](#componentsObject) | An element to hold various schemas for the specification.
<a name="A2SComponents"></a>components | [Components Object](#componentsObject) | An element to hold various reusable objects for the specification. Everything that is defined inside this object represents a resource that MAY or MAY NOT be used in the rest of the document and MAY or MAY NOT be used by the implemented [Application](#definitionsApplication).
Copy link
Member

Choose a reason for hiding this comment

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

I think makes sense to also add this clarification under Components Object description.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup, agree. Would you mind opening the PR?

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.

None yet

6 participants