feat: add topic extension - #182
Open
huynguyengl99 wants to merge 1 commit into
Open
Conversation
huynguyengl99
requested review from
asyncapi-bot-eve and
derberg
as code owners
August 11, 2026 08:15
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
|
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
1 participant
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.
Adds the
topicextension.Multiplexed transports carry many logical streams over one connection, which AsyncAPI models as several channels sharing an
address- the Kraken example in the spec repository does exactly this, with seven channels at/. There is currently no way to express which stream a channel is, or how a client addresses it, so that information lives in prose. This extension carries it.parametersdoes not cover the case: the specification permits it only when the address contains Channel Address Expressions, and here the address is the connection rather than the topic.Implemented and in use in chanx, which generates it for topic-based WebSocket routes and consumes it when generating typed clients.