feat!: remove messageId() #889
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
fmvilas
requested review from
magicmatatjahu,
jonaslagoni,
smoya and
asyncapi-bot-eve
as code owners
|
Kudos, SonarCloud Quality Gate passed!
|
jonaslagoni
reviewed
Nov 4, 2023
There was a problem hiding this comment.
Just one question, same as in asyncapi/parser-api#102 (comment)
|
/rtm |
|
🎉 This PR is included in version 3.0.0-next-major-spec.8 🎉 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
Removes the
messageId()function from the Message and MessageTrait objects. Keeps the same behavior on v2 but it doesn't look formessageIdon v3. Now we only have one method to grab the id of a message and it's.id().Also, now
.hasMessageId()now always returnsfalsefor v3.Related issue(s)
asyncapi/spec#978