Jeremy Fiel

is it possible to assert `defined` on the `property: parameters` in the `where` clause? If they are valid in more than one place, you would need two separate rules. Although,...

@lornajane I'm not sure I agree with your comment >The parameter object itself is therefore the location of the problem... The problem lies in the location where a reusable component...

some additional context on why I raised this, using the VS Code extension in the design phase, in the `problems` tab, you can click the error and it will navigate...

this is related to bundling or flattening and is a hot topic in the JSON Schema community. It was undefined behavior for quite a few years and only recently have...

Hi @tatomyr comparing your branch with ajv, it doesn't appear you have fixed the dynamic referencing bug which I linked. Speed is great but if it doesn't conform to the...

ok, so another interesting twist on this validation.. the spec states `encoding` is only valid for `request object` and `multipart` or `application/x-www-form-urlencoded` i was trying to add it to a...

...

i figured it out .. i was missing the headers mapping key ```json "content": { "multipart/mixed": { "schema": { "type": "object", "properties": { "file": { "type": "string", "format": "binary" },...

related https://github.com/Redocly/redoc/issues/2444

Sure, the rule works ok but this should be part of the OAS validation by the tooling. It's part of the spec that's not validated today by Redocly, as far...