Skip to content

test: cover reply channel with null address#1184

Draft
YforC wants to merge 1 commit into
asyncapi:masterfrom
YforC:test-reply-null-address-channel
Draft

test: cover reply channel with null address#1184
YforC wants to merge 1 commit into
asyncapi:masterfrom
YforC:test-reply-null-address-channel

Conversation

@YforC

@YforC YforC commented Jun 9, 2026

Copy link
Copy Markdown

Why

Issue #876 describes a resolved-document validation edge case where an operation reply uses address.location and references a reply channel whose address is null. Current master already accepts this scenario, but there was no focused regression coverage for it.

Related to #876.

What Changed

Added a v3 resolved validation test showing that a reply channel with address: null is valid when the reply address is supplied via address.location.

Verification

  • npm install
  • npx jest test/ruleset/rules/asyncapi-document-resolved.spec.ts --runInBand
  • npm run parser:build

npm run parser:test:unit still has existing external-reference timeout failures unrelated to this test.

@changeset-bot

changeset-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: eaa74bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@sonarqubecloud

sonarqubecloud Bot commented Jun 9, 2026

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.

1 participant