openapi-spec-validator icon indicating copy to clipboard operation
openapi-spec-validator copied to clipboard

OpenAPI Spec Validator is a CLI, pre-commit hook and python package that validates OpenAPI Specs against the OpenAPI 2.0 (aka Swagger), OpenAPI 3.0 and OpenAPI 3.1 specification.

Results 79 openapi-spec-validator issues
Sort by recently updated
recently updated
newest added

Hi, I noticed that there is a breaking change from `0.2.9` to `0.3.0`, but I am not sure if it is intentional or not. **tl;dr**: an integer is no longer...

The resolution for issue #96 (duplicated OperationID not detected) introduced a breaking-change or regression. Upon updating dependencies to version 0.3.0, the connexion library now reports this error when I run...

Current SwaggerHub implementation exports YAMLs with responses looking like: ```yaml responses: 200: description: success ``` This leads openapi-spec-validator to fail trying to apply a regex to the 200 status code....

Is it possible with the openapi-spec-validator to remove the "$id" and "$schema" from referred schemata before handling them to the validators. JSON schemata allow these two keys (and at least...

We are running a pyramid app with the following open api yaml definition : ```yaml openapi: 3.0.1 info: title: Sample API contact: name: API Support email: [email protected] version: 1.0.0 x-audience:...

I want to validate and get a json with all $ref resolved, how can I get this?

Hello, I don't understand the following validation error: ``` {'{$response.header.Location}': {'get': {'requestBody': {}, 'responses': {'301': {'x-scope': ['', '#/components/callbacks/moveProgress'], '$ref': '#/components/responses/MoveProgress'}, '303': {'x-scope': ['', '#/components/callbacks/moveProgress'], '$ref': '#/components/responses/MoveSuccess'}}}}} is not valid under...

I have a spec which this project reports as valid where other validators, such as speccy, do not. What I've found is that the spec we were using had duplicate...

Note: I am not entirely sure if the source of this issue lies within the scope of this library of any of its dependencies. ## Situation My (openAPI specification) JSON...