Skip to content

format and ruleset: AsyncAPI #965

@philsturgeon

Description

@philsturgeon

User story.
As an AsyncAPI, I will get validation and a reasonable set of default opinions when working with AsyncAPI files.

Is your feature request related to a problem?
Right now spectral doesn't know what AsyncAPI is. It'll recognize $ref'ed schema files, but not the main thing, so I cannot write rules for channel names, etc.

Describe the solution you'd like

A ruleset based on OpenAPI (started here apisyouwonthate/style-guide#4).

AsyncAPI is important enough that it should be another core ruleset, not done over at openapi-contrib. We will almost certainly split rulesets out into their own NPM modules in the future, but for now, let's get this one in the core.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions