Skip to content

fix: parse schemas in operation channels - #1250

Open
abdu1lah26 wants to merge 2 commits into
asyncapi:masterfrom
abdu1lah26:explore-parser
Open

abdu1lah26 wants to merge 2 commits into
asyncapi:masterfrom
abdu1lah26:explore-parser

Conversation

@abdu1lah26

Copy link
Copy Markdown

Summary

  • Add schema paths for payloads and headers inside operations.*.channel.messages.*.
  • Add a regression test covering an external operation channel reference with a custom schema parser.

Testing

  • npm test -- parse-schema-v3.spec.ts --coverage=false

Related Issue

Fixes #1099

@changeset-bot

changeset-bot Bot commented Sep 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 41b66c3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@asyncapi/parser Patch

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

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@sonarqubecloud

Copy link
Copy Markdown

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] Custom Parsers aren't triggered on payloads that are defined though Operations.Channel

1 participant