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
Whilst the openapi spec allows HTTP codes for responses objects to be of type 2XX or 4XX (link) indicating a range of codes, this sphinx contrib seems unable to use those response codes appearing in a spec, with a warning:
(ERROR/3) HTTP status code must be an integer (e.g. 200) or start with an integer (e.g. 200 OK); <#text: '4XX'> is invalid
Not sure if the issue originates in the sphinxcontrib.openapi or in a dependency.
Way to reproduce: use an openapi.yaml spec with something like this in its paths:
Whilst the openapi spec allows HTTP codes for responses objects to be of type 2XX or 4XX (link) indicating a range of codes, this sphinx contrib seems unable to use those response codes appearing in a spec, with a warning:
(ERROR/3) HTTP status code must be an integer (e.g.
200) or start with an integer (e.g.
200 OK); <#text: '4XX'> is invalid
Not sure if the issue originates in the sphinxcontrib.openapi or in a dependency.
Way to reproduce: use an openapi.yaml spec with something like this in its paths:
The text was updated successfully, but these errors were encountered: