We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validate
When using the bump validate command it could make sense to add a --strict flag to enable OpenAPI/AsyncAPI spec verification.
bump validate
--strict
oas-validator
@asyncapi/openapi-schema-parser
@asyncapi/parser
The text was updated successfully, but these errors were encountered:
deploy
We should probably use https://github.com/stoplightio/spectral to delegate validation to the formal specs directly
Sorry, something went wrong.
Spectral certainly has more rulesets built already, but Redocly CLI has an interesting approach which is easier to work with. Preview of a post I've done on the tool showing off a bit of the linting. https://apisyouwonthate.com/p/9cee6154-f443-4c4c-8163-b76be3c55d3f/
Remember there's more than just "linting YAML" or "linting OpenAPI", using some of these rulesets moves you into API Security testing and compliance.
https://github.com/stoplightio/spectral-rulesets
And you move into API Governance if custom rulesets are being used:
https://apisyouwonthate.com/blog/automated-style-guides-for-rest-graphql-grpc/
No branches or pull requests
When using the
bump validate
command it could make sense to add a--strict
flag to enable OpenAPI/AsyncAPI spec verification.oas-validator
library@asyncapi/openapi-schema-parser
@asyncapi/parser
The text was updated successfully, but these errors were encountered: