Jeremy Whitlock

I will probably allow you to provide an `options.validator` which will allow you to pass options to z-schema. It follows the same convention we currently follow for `options.jsonRefs`, which are...

I'm not completely against it but I do describe a specific error/warning structure that would need to be adhered to, along with not breaking existing code in the validators that...

Well, the objects in the `errors` and `warnings` response needs to be a specific structure too because how would any library using Sway have any consistency? I couldn't write a...

Also, as for your wanting to use JSON Schema v5, how do you expect that to work if OpenAPI/Swagger doesn't support it?

I'm all for pluggability where it makes sense, I've stated this. But the reasoning you want this pluggability does not make sense to me and here's why. OpenAPI does not...

I told you I wasn't against it but you said something that was inaccurate and I wanted to clear that up in case that was the sole reason you were...

I will try to figure out how best to handle this. The only real _interface_ here is that the returned validation error structures.

I looked into making the validator pluggable and it's not hard. I'm just trying to wrap up 3.x support first. I thought I'd do this as a part of 3.x...

I'm not sure I want to support custom Swagger documents. I'm not completely against it but since we already give you APIs for [registering custom validators](https://github.com/apigee-127/sway/blob/master/docs/API.md#module_Sway..SwaggerApi+registerValidator) and will soon have...

The point I made is that sway already has an API to register custom validators, so validations for custom extensions and other stylistic checks that are not covered by the...