Jeremy Whitlock

I'm fixing it in both.

I'll merge it in when I am planning the next release. That should be soon.

This is a great idea. We already do this when [validating the spec](https://github.com/apigee-127/swagger-tools/blob/master/lib/helpers.js#L61) but we do not do it when we manually validate a schema.

Validating the spec validates that your Swagger document is valid itself. When the middleware does request/response validation, it uses a similar approach but not the exact same logic. I think...

When I rewrote the API in `sway`, you'll see that [it handles this as you'd expect](https://github.com/apigee-127/sway/blob/master/lib/types/operation.js#L236) by validating every parameter regardless of whether a previous parameter had failed. In `swagger-tools`,...

I could do it pretty quickly but a PR would expedite things.

I've not made much progress on it. I rewrote `json-refs` and I'm in the process of getting `swagger-tools` and `sway` updated to the latest `json-refs` first. Then I'll fix bugs...

PRs are always welcome. The changes I need to make for `json-refs` won't touch this code so it would be without conflict. My typical release process is this: 1. Update...

I'll give this a peek.

This is unlikely. Long story short, implementing this yourself in your own middlewares would be very, very simple and any enhancements to `swagger-tools` right now is not likely due to...