Skip to content

fix: add missing required fields to AsyncAPI examples (issue #1174)#1181

Closed
Midhat-kazmi wants to merge 1 commit intoasyncapi:masterfrom
Midhat-kazmi:fix-issue-1174-missing-required-fields
Closed

fix: add missing required fields to AsyncAPI examples (issue #1174)#1181
Midhat-kazmi wants to merge 1 commit intoasyncapi:masterfrom
Midhat-kazmi:fix-issue-1174-missing-required-fields

Conversation

@Midhat-kazmi
Copy link

Fixes #1174

This PR updates AsyncAPI 3.0 examples to include all required fields
as defined in the specification schemas.

The changes ensure that examples are valid and aligned with the spec,
making them easier to understand and use.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 7, 2026

@Midhat-kazmi
Copy link
Author

Hi everyone! Just a gentle note that this PR fixes #1174 by aligning
AsyncAPI 3.0 examples with required fields in the spec.
Happy to adjust anything if needed. Thanks!

@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.

🐞 Bug: Example message schemas in AsyncAPI 3.0 spec missing required fields

3 participants