You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Support literal curly braces in channel addresses #1241
There is no supported way to mark curly braces as literal characters. However, MQTT, AMQP, and other protocols may use curly braces as ordinary characters in topic names, routing keys, queue names, and other channel addresses. As a result, literal addresses cannot be distinguished from AsyncAPI parameter expressions when channel parameter validation runs.
Please add and document an unambiguous way to represent literal curly braces and exclude them from parameter extraction in both AsyncAPI v2 and v3.
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.
Activity
github-actions commentedon Aug 30, 2026
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.