Skip to content

fix: add missing name and title fields to Multi Format Schema Object Avro example (#1174)#1183

Closed
Anirudh-x wants to merge 1 commit intoasyncapi:masterfrom
Anirudh-x:fix/issue-1174-missing-required-fields
Closed

fix: add missing name and title fields to Multi Format Schema Object Avro example (#1174)#1183
Anirudh-x wants to merge 1 commit intoasyncapi:masterfrom
Anirudh-x:fix/issue-1174-missing-required-fields

Conversation

@Anirudh-x
Copy link

@Anirudh-x Anirudh-x commented Feb 19, 2026


Fix: add missing name and title fields to Multi Format Schema Object Avro example

The myMessage example in the Multi Format Schema Object - Avro section of spec/asyncapi.md was missing the name and title fields. This makes the example incomplete and inconsistent with how a proper AsyncAPI message object should look, potentially misleading developers who use the spec examples as implementation references.

Changes made:

  • Added name: UserCreated to the myMessage example
  • Added title: User created event to the myMessage example

Related issue(s): #1174


…Avro example (asyncapi#1174)

The myMessage example under channels.example.messages in the Multi Format
Schema Object - Avro section was missing the name and title fields, making
it an incomplete and potentially misleading example for users.

Added:
- name: UserCreated
- title: User created event

Fixes asyncapi#1174
Copilot AI review requested due to automatic review settings February 19, 2026 10:36
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@sonarqubecloud
Copy link

@derberg
Copy link
Member

derberg commented Feb 24, 2026

Thanks for the contribution. I’m closing this PR because, while there is an existing issue, it was not approved or opened for contribution before the pull request was submitted.

Please make sure to follow the contribution guidelines, which explain when issues are considered ready for implementation and when pull requests are appropriate.

@derberg derberg closed this Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants