UNPKG

@apisyouwonthate/style-guide

Version:

Make your HTTP APIs better, faster, stronger, whether they are still being designed (API Design-First) or your organization has flopped various mismatched APIs into production and now you're thinking some consistency would be nice. Using Spectral and Open

71 lines (66 loc) 1.56 kB
import { DiagnosticSeverity } from "@stoplight/types"; import testRule from "./__helpers__/helper"; testRule("hosts-https-only-oas2", [ { name: "valid case", document: { swagger: "2.0", info: { version: "1.0" }, paths: { "/": {} }, host: "example.com", schemes: ["https"], }, errors: [], }, { name: "an invalid server.url using http", document: { swagger: "2.0", info: { version: "1.0" }, paths: { "/": {} }, host: "example.com", schemes: ["http"], }, errors: [ { message: "Schemes MUST be https and no other protocol is allowed.", path: ["schemes", "0"], severity: DiagnosticSeverity.Error, }, ], }, { name: "an invalid server.url using http and https", document: { swagger: "2.0", info: { version: "1.0" }, paths: { "/": {} }, host: "example.com", schemes: ["https", "http"], }, errors: [ { message: "Schemes MUST be https and no other protocol is allowed.", path: ["schemes", "1"], severity: DiagnosticSeverity.Error, }, ], }, { name: "an invalid server using ftp", document: { swagger: "2.0", info: { version: "1.0" }, paths: { "/": {} }, host: "example.com", schemes: ["ftp"], }, errors: [ { message: "Schemes MUST be https and no other protocol is allowed.", path: ["schemes", "0"], severity: DiagnosticSeverity.Error, }, ], }, ]);