Andrew Tatomyr

This is interesting. Schema could contain other schemas, and in your examples, you might be referring to a nested schema. If you aren't using the `where` clause, it propagates further...

Hi @simon-spinner! It looks like you know how to fix that. Just in case, we accept pull requests here 😉

Hi @steve-nay-sage! By default, we treat all schemas as closed. So you have two options: either add the `additionalProperties: true` to make them explicitly open or tweak the rule to...

You're correct: schemas are open by default as per specification. However, for that particular rule, this behaviour doesn't allow catching typos. Imagine the following case: ```yaml openapi: 3.0.3 paths: /test:...

Update. Probably we can catch cases like this and modify the rule's behaviour appropriately.

Oh, this is indeed a corner case. Nevertheless, I think it is still worth fixing. Thank you for bringing this up!

This looks like a bug. Thank you for finding this!

Good point on the `containsAny`! If there's no other suggestions, let's go with yours.

> And contains would mean it contains them all? Yes, the same way the `required` assertion works.

Hi @ootkin! Thanks for bringing this up. What output would you expect in the joined file in this example?