fix: clarify expected type for Message headers #952
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
smoya
requested review from
fmvilas,
derberg,
dalelane,
char0n and
asyncapi-bot-eve
as code owners
smoya
changed the title
|
@fmvilas would you mind taking a look to this? 🙏 |
derberg
approved these changes
Jul 20, 2023
|
please do not merge before #939 as release is somehow broken and RC for traits for example was not out |
|
Kudos, SonarCloud Quality Gate passed!
|
|
/rtm |
asyncapi-bot
merged commit e2a3fa4
into
asyncapi:next-major-spec
16 of 17 checks passed
|
🎉 This PR is included in version 3.0.0-next-major-spec.13 🎉 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
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.
Comes from #948 (comment)
This PR clarifies the expected type and shape for Message headers.