Repository navigation
feat(reference): add support for AsyncAPI 3.1.0 - #5263
Merged
robert-hebel-sb merged 2 commits intoOct 21, 2026
Merged
Conversation
The AsyncAPI 3 parsers and dereference strategy take their media types from apidom-ns-asyncapi-3, so they handle 3.1.0 documents without source changes. Document the asyncapi-json-3 and asyncapi-yaml-3 parsers and the asyncapi-3 dereference strategy with their 3.0.0 and 3.1.0 media types in the README, which did not list AsyncAPI 3 yet. Bump the AsyncAPI 3 parser and dereference fixtures to 3.1.0, keep a 3.0.0 media type check in the parser tests, and add dereference fixtures for ROS 2 server and operation bindings. ROS 2 binding fields cannot hold Reference Objects, so the dereference visitor needs no change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robert-hebel-sb
force-pushed
the
feat/asyncapi-3.1.0/phase-3
branch
from
October 19, 2026 08:49
bdf8986 to
9f8ab2f
Compare
glowcloud
approved these changes
Oct 19, 2026
| assert.deepEqual(toValue(actual), expected); | ||
| }); | ||
| }); | ||
| context('given ROS 2 binding in Operation Object', function () { |
Contributor
There was a problem hiding this comment.
I feel like this test is a bit redundant, considering that all bindings work the same way 🤔 If we want to keep it, maybe we should instead add it to the existing fixtures, as that would test all paths (components, operation trait, operation), instead of just operation? But IMO it's not needed at all. Same goes for Server Bindings.
Contributor
Author
There was a problem hiding this comment.
Agreed & removed
Dereferencing resolves the $ref at the bindings container level and never inspects binding values, so ROS 2 follows the same path as the existing fixtures. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 3 of 4 for AsyncAPI 3.1.0 support: apidom-reference.
Depends on #5262 (stacked; base is
feat/asyncapi-3.1.0/phase-2).Changes
asyncapi-json-3/asyncapi-yaml-3parsers and theasyncapi-3dereference strategy take their media types fromapidom-ns-asyncapi-3, so 3.1.0 documents are handled without source changes.asyncapi-json-3andasyncapi-yaml-3parser sections and theasyncapi-3dereference strategy section with their 3.0.0 and 3.1.0 media types (AsyncAPI 3 was only mentioned in the execution order examples so far).asyncapi-json-3/asyncapi-yaml-3bumped to 3.1.0;canParsealso asserts the 3.0.0 media type."asyncapi": "3.1.0"(116 files);schemaFormatvalues with version 3.0.0 are kept.components. ROS 2 binding fields can't hold Reference Objects, so the dereference visitor is unchanged.Verification
grep -c "version=3.1.0" README.md> 0Known gaps
🤖 Generated with Claude Code