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
User story.
As an architect of our company' central AsyncAPI document registry, I want to be certain, that our AsyncAPI files follow the spec. In this case, we received AsyncAPI files that do not comply to the operation's message rules.
Is your feature request related to a problem?
Some AsyncAPI files used in our company use wrong references (from other channels). According to https://www.asyncapi.com/docs/reference/specification/v3.0.0#operationsObject, messages in operation objects must only be referenced from the operations' channel object messages.
Describe the solution you'd like
I would like to see a rule in the standard rule set.
Additional context
I could not find a way to solve this using the core functions.
The text was updated successfully, but these errors were encountered:
User story.
As an architect of our company' central AsyncAPI document registry, I want to be certain, that our AsyncAPI files follow the spec. In this case, we received AsyncAPI files that do not comply to the operation's message rules.
Is your feature request related to a problem?
Some AsyncAPI files used in our company use wrong references (from other channels). According to https://www.asyncapi.com/docs/reference/specification/v3.0.0#operationsObject, messages in operation objects must only be referenced from the operations' channel object messages.
Describe the solution you'd like
I would like to see a rule in the standard rule set.
Additional context
I could not find a way to solve this using the core functions.
The text was updated successfully, but these errors were encountered: