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
The latest version of swagger-spec-validator now validates that defaults are the correct type.
Since the library is not pinned, the release has broken master.
(tests/test_api.py::test_other_errors_stop_application_to_setup) relies on the old behavior (don't exit on default type errors if app(debug=true))
Also, one of the test fixtures has a (type: array) without an items: ... block, which is now invalid.
Additional info:
#611 fixes the build by upgrading to the latest version.
An alternate approach would be to pin to 2.0.2 of swagger-spec-validator
Let me know if that's preferred and I can put up a PR.
The text was updated successfully, but these errors were encountered:
dtkav
pushed a commit
to dtkav/connexion
that referenced
this issue
Jul 2, 2018
Description
The latest version of swagger-spec-validator now validates that defaults are the correct type.
Since the library is not pinned, the release has broken master.
(tests/test_api.py::test_other_errors_stop_application_to_setup) relies on the old behavior (don't exit on default type errors if
app(debug=true)
)Also, one of the test fixtures has a (type: array) without an
items: ...
block, which is now invalid.Additional info:
#611 fixes the build by upgrading to the latest version.
An alternate approach would be to pin to 2.0.2 of swagger-spec-validator
Let me know if that's preferred and I can put up a PR.
The text was updated successfully, but these errors were encountered: