Conversation
glowcloud
reviewed
Jan 15, 2026
packages/apidom-ls/src/config/asyncapi/message-trait/lint/index.ts
Outdated
Show resolved
Hide resolved
packages/apidom-ls/src/config/asyncapi/message-trait/lint/index.ts
Outdated
Show resolved
Hide resolved
packages/apidom-ls/src/config/asyncapi/message-trait/lint/headers-3-0--type.ts
Outdated
Show resolved
Hide resolved
packages/apidom-ls/src/config/asyncapi/message-trait/lint/allowed-fields-3-0.ts
Outdated
Show resolved
Hide resolved
packages/apidom-ls/src/config/asyncapi/info/lint/allowed-fields-3-0.ts
Outdated
Show resolved
Hide resolved
packages/apidom-ls/src/config/asyncapi/operation-trait/documentation.ts
Outdated
Show resolved
Hide resolved
23 tasks
glowcloud
approved these changes
Jan 16, 2026
Contributor
glowcloud
left a comment
There was a problem hiding this comment.
Seems fine, just one change and the failing test needs to be adjusted.
packages/apidom-ls/src/config/asyncapi/components/documentation.ts
Outdated
Show resolved
Hide resolved
…ncapi3-with-compatible-properties
lukaszzazulak
approved these changes
Jan 19, 2026
robert-hebel-sb
approved these changes
Jan 19, 2026
robert-hebel-sb
pushed a commit
that referenced
this pull request
Jan 19, 2026
Add complete configuration for AsyncAPI 3.0.0 root object keywords following the conventions from PR #5095: - allowed-fields: Define valid root-level fields for AsyncAPI 3 - completion: Add autocomplete support for all root fields - documentation: Add specification links and field descriptions Key changes for AsyncAPI 3.0.0: - Added 'operations' field (new in v3) - Removed 'tags' and 'externalDocs' from root (moved to info object in v3) - Updated all documentation links to v3.0.0 specification Root object fields now supported: - asyncapi (required) - id - info (required) - servers - defaultContentType - channels - operations (new in v3) - components
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
6 participants
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.
This PR is for OSS-250 and OSS-251
Note:
Channel, Operations and Messages will be handled in OSS-245
Description
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Checklist
My PR contains...
src/is unmodified: changes to documentation, CI, metadata, etc.)package.json)My changes...
Documentation
Automated tests