feat(asyncapi): derive message ownership from operation action#411
Open
freaz wants to merge 1 commit into
Open
feat(asyncapi): derive message ownership from operation action#411freaz wants to merge 1 commit into
freaz wants to merge 1 commit into
Conversation
Without an explicit x-eventcatalog-role, a send/publish operation owns the message while a receive/subscribe operation only references it - documented if missing, but never overwriting an entry owned by another service. Explicit roles (provider/client) and single-service catalogs are unaffected.
|
|
🦋 Changeset detectedLatest commit: 473d16c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
EventCatalog models a message as a single shared contract, but the AsyncAPI generator treated every service as the owner of every message it referenced, so whichever service was generated last would overwrite the message's catalog entry — letting a subscriber clobber the publisher's summary, schema, and badges. AsyncAPI already expresses producer/consumer intent through the operation action (send vs receive), so we now use that signal to decide ownership: senders own and may overwrite the contract, while receivers only reference it. This keeps the published contract authoritative and stable regardless of generation order, without breaking existing setups — explicit x-eventcatalog-role still wins and single-service catalogs are unaffected.