Adam Altman

(I converted it to a draft because I come to check this PR every week and forget it is still in progress. 🧠 )

`no-illogical-schemas` could be a potential name for the rule. We could also check `allOf` for illogical behavior: https://json-schema.org/understanding-json-schema/reference/combining#illogicalschemas

It is indeed illogical too. If possible values intersect, they are illogical in the context of `oneOf`. I don't know what you mean by the intentional use of `oneOf` to...

@tatomyr I think the schema is written incorrectly for "I want 15 to be invalid" and the user would need to compose of more complex objects with `not` multiple of...

@jasonbarry we withheld the docs because we are expecting a configuration option to change and want to support a unified configuration file across our entire product suite. I believe we'll...

We'll close it once we ship the docs. Thanks.

Also, ``` Component: "MySchema" is never used. 10 | schemas: 11 | 12 | MySchema: 13 | x-tags: 14 | - my-tag Warning was generated by the no-unused-components rule. ```...

What about making the `operationPath` an extension so that tooling providers can decide whether or not to implement it? It would encourage more use of `operationId` and make APIs "more...

This could be handled initially through specification extension. At what level would the link occur (root, operation, etc)? Would it link to a specific workflow ID or to an entire...

It would be nice if we mocked this too.