Array minItems not respected on anyOf

[rubensa]

Array minItems not respected on anyOf

[chohmann]

@rubensa The current behavior you outlined is the correct behavior and there is no issue with it.

This request body:

{
  "property1": [],
  "property2": [1, 2]
}

matches the second child of the anyOf because it is lacking additionalProperties: false. Because that schema allows for additional properties to be present, the property1 is considered an additionalProperty, even though it matches the first anyOf child's schema. You'd get the same behavior if the request body contained something random, that doesn't match the first anyOf child:

{
  "somethingRandom": 1,
  "property2": [1, 2]
}

You can check this in any online json schema validator, (e.g. https://www.jsonschemavalidator.net/).