From 75eb2e1afb1186151cc14bfe8142f8490f53e112 Mon Sep 17 00:00:00 2001 From: "Jarzyna, Andrzej" Date: Tue, 3 Dec 2019 12:55:12 +0100 Subject: [PATCH] Get example inline with rules naming change --- general-guidelines/validating-api-descriptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/general-guidelines/validating-api-descriptions.md b/general-guidelines/validating-api-descriptions.md index 0a44d63..24d5d47 100644 --- a/general-guidelines/validating-api-descriptions.md +++ b/general-guidelines/validating-api-descriptions.md @@ -68,7 +68,7 @@ Spectral defines 4 levels of problem severity: Currently any problem of severity of error or warning will cause a failure status code of `1`. This means that any `error` or `warning` in your specification will prevent your CI/CD pipeline from succeeding. During design process you may want to ignore certain warnings, such as the runtime information (e.g. `hosts` or `servers`). In order to do that you can add a `--skip-rule` flag: ``` -spectral lint my-api-spec.yaml --skip-rule=protocol-https-only-oas3 +spectral lint my-api-spec.yaml --skip-rule=adidas-oas3-protocol-https-only ``` ## Spectral rules list