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
{{ message }}
This repository was archived by the owner on Jul 9, 2021. It is now read-only.
This will be useful to detect cases where for instance, doesn't have a default response, and the response status "mistakenly" uses a status code that is not defined in the specs.
At OperationValidator.validateBody, if it doesn't find a response validator, it stops without error. It will be interesting to have the option (via parameter/flag) to raise an exception if the status code is not in the specs.
Right now as a workaround I doing that validation beforehand (similar to getResponseValidator) what becomes redundant when it rechecks the body. Also, if has any other option that has a similar effect, please let me know.
This will be useful to detect cases where for instance, doesn't have a default response, and the response status "mistakenly" uses a status code that is not defined in the specs.
At
OperationValidator.validateBody, if it doesn't find a response validator, it stops without error. It will be interesting to have the option (via parameter/flag) to raise an exception if the status code is not in the specs.Right now as a workaround I doing that validation beforehand (similar to
getResponseValidator) what becomes redundant when it rechecks the body. Also, if has any other option that has a similar effect, please let me know.