fix: inconsistancy in components #403
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonaslagoni
requested review from
fmvilas,
derberg,
dalelane,
smoya,
char0n and
asyncapi-bot-eve
as code owners
fmvilas
approved these changes
Jun 26, 2023
|
/rtm |
|
/rtm |
|
Kudos, SonarCloud Quality Gate passed!
|
|
Thanks @fmvilas 🙏 |
|
🎉 This PR is included in version 5.0.0-next-major-spec.21 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 6.0.0-next-major-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR cleanup some inconsistencies in components.
schemascould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$serverscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$channelscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$serverVariablescould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$parameterscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$operationTraitscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$messageTraitscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$serverBindingscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$channelBindingscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$operationBindingscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$messageBindingscould be defined with any name, now it matches the regular expression: ^[a-zA-Z0-9.-_]+$operationTraitscould not be defined with references.messageTraitscould not be defined with references.serverBindingscould not be defined with references.channelBindingscould not be defined with references.operationBindingscould not be defined with references.messageBindingscould not be defined with references.