openapi-spec-validator fails for integer response codes

Open
#79 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi, python
Domain
api, tooling

Research direction

Reproduce the failure with the SwaggerHub-style YAML response using an integer status code and inspect where openapi-spec-validator applies a regex to that code. The work is done when this input validates successfully without breaking validation of other response codes.

Written by the indexing model from the issue text.

Description

Current SwaggerHub implementation exports YAMLs with responses looking like:

responses:
    200:
        description: success

This leads openapi-spec-validator to fail trying to apply a regex to the 200 status code. Assuming what SwaggerHub exports is correct, openapi-spec-validator should not fail on such an input...

Dominant language
Python
Stars
409
Forks
73
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python-openapi/openapi-spec-validator

All issues in python-openapi/openapi-spec-validator

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.