fix: trigger custom schema on messages only defined in a channel of an operation

[liam-oldershaw-ctct]

Description

• Triggers the custom parser for Messages that are defined inside of the channel of an operation

Related issue(s)
Resolves: #1099

[changeset-bot]

⚠️ No Changeset found

Latest commit: a87a06a

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

[github-actions]

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.

[fmvilas]

That's a great catch. Appreciate the fix 🙏 Would you mind adding tests to cover this so it won't happen again by mistake?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[liam-oldershaw-ctct]

@fmvilas while writing the unit test I've noticed that the schema also doesn't get an anonymous id like the tests above.. So that might be another issue (not sure how important though)

[fmvilas]

@fmvilas while writing the unit test I've noticed that the schema also doesn't get an anonymous id like the tests above.. So that might be another issue (not sure how important though)

You probably caught another issue, yeah. Would you mind adding a separate PR for that? I think a small and focused PR is always better.

[liam-oldershaw-ctct]

@jonaslagoni, @magicmatatjahu, and/or @smoya. can i get eyes on this please. I'll spend some time on the other issue

Edit: Ahh, i see the issue around updating the repo maintainers. Apologies, All good