Chris Olson

In your example, did you mean for: `"target": { "$ref": "#/definitions/sql" }` to be: `"sql": { "$ref": "#/definitions/sql" }`

I've encountered the same issue. I'm pretty sure the problem is somewhere in `helpers.js` and its `makeTree` or `filterRedundant` methods - I think these methods are trying to be too...

@buremba responding to your original question, I think the error you're expecting is in the AJV results, it's just not returned by better-ajv-errors: `"message":"should match exactly one schema in oneOf"`

Yes, exactly, I'd like the config option to do the implementation myself. We have an OAS framework that uses koa-oas3 to wire up routes per OAS operation endpoint. For example,...

@ferdikoomen yes, you have it exactly right. Thanks for considering!

yup 0.12.0 fixed my issues too 👏

I'm curious why people are asking for this. If it's "read only", then they can't update it, and why have it as part of the incoming (POST or PATCH) defined...

Posted this in another thread..a solution perhaps (for now) I bugged alarm.com about the annoying two-factor messaging every time I logged on. They responded, telling me I could contact my...

@supertong yes you're right, in our case it was on a path param, but I think this was a mistake on our part. In other words, `readonly:true` on a path...

🥳 very exited for this!