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
Validating an OpenAPI specification file is as simple as putting extends: "spectral:oas" into a .yaml file, and passing this in as a parameter when calling spectral lint.
I have a use case where I don't have an OpenAPI specification inside a file, but just a plain JSON schema which I'd check for consistency? Is that possible? Given the fact that the spectral:oas ruleset relies on JSON Schema, and the draft-2020-12 JSON schema definition is even included in the source tree, this should be rather straight-forward, right? Is it exposed as functionality somewhere? I tried using spectral:jsonschema and spectral:json-schema, but none of these worked.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Validating an OpenAPI specification file is as simple as putting
extends: "spectral:oas"
into a.yaml
file, and passing this in as a parameter when callingspectral lint
.I have a use case where I don't have an OpenAPI specification inside a file, but just a plain JSON schema which I'd check for consistency? Is that possible? Given the fact that the
spectral:oas
ruleset relies on JSON Schema, and thedraft-2020-12
JSON schema definition is even included in the source tree, this should be rather straight-forward, right? Is it exposed as functionality somewhere? I tried usingspectral:jsonschema
andspectral:json-schema
, but none of these worked.Beta Was this translation helpful? Give feedback.
All reactions