Upgrade to swagger-spec-validator 2.3.1 (fixes #612)

[dtkav]

Master is boken because of an update to swagger-spec-validator. This upgrades to the latest version and should fix the build.

Changes proposed in this pull request:

• upgrade to swagger-spec-validator 2.3.1
• debug=true will no longer continue if an operation has invalid defaults (change was in swagger-spec-validator)

[hjacobs]

Is there any way to get the debug=true behavior back? It's pretty useful for quick iterations during development when the spec is being changed and temporarily (partly) broken.

[dtkav]

@hjacobs I can hard-pin (==) to 2.0.1 instead to preserve the previous behavior if you prefer that.

The only real change here is that default validation happens earlier. Personally I'd prefer for it to crash as early as possible when the spec is wrong, because then you know the problem is unrelated to connexion, and there are several tools available for debugging invalid specs.

The previous behavior would have avoided crashing in Operation.validate_defaults(), which also made sense given the lack of functionality in the spec validator.

Another way to handle you request would be to ignore all validation errors in apis/abstract.py, but that seems like a recipe for heaps of stack traces 🙂 .

[hjacobs]

👍

[jmcs]

👍