false-negative report on `anyOf` if two arrays have different length

[6293]

{
  "lhs": {
    "anyOf": [{"type": "integer", "minimum": 1}]
  },
  "rhs": {
    "anyOf": [{"type": "integer", "minimum": 1}, {"type": "integer", "maximum": 1}]
  }
}

this does not produce diff. likely because of here, zip will stop as soon as one of iterators stops producing values.

[6293]

{
  "lhs": {
    "anyOf": [{"type": "integer"}]
  },
  "rhs": {
    "anyOf": [{"type": "integer"}, {"type": "string"}]
  }
}

this does produce diff because if a different type has been added, it is caught in diff_instance_types

[6293]

Two examples below are breaking changes (we don't support allOf for now though):

{
  "lhs": {
    "anyOf": [{"type": "integer", "minimum": 5, "maximum": 6}]
  },
  "rhs": {
    "anyOf": [{"type": "integer", "minimum": 3, "maximum": 4}]
  }
}

{
  "lhs": {
    "allOf": [{"type": "integer", "minimum": 5, "maximum": 6}]
  },
  "rhs": {
    "allOf": [
      {"type": "integer", "minimum": 5, "maximum": 6}, 
      {"type": "integer", "minimum": 1, "maximum": 2}
    ]
  }
}

but this is not:

{
  "lhs": {
    "anyOf": [{"type": "integer", "minimum": 5, "maximum": 6}]
  },
  "rhs": {
    "anyOf": [
      {"type": "integer", "minimum": 5, "maximum": 6}, 
      {"type": "integer", "minimum": 1, "maximum": 2}
    ]
  }
}

With the current implementation ChangeKind::is_breaking is not sure if a provided RangeAdd is a breaking change or not. Maybe we should add is_breaking field on RangeAdd (and on other type-specific constraint additions)?

[6293]

is_breaking is false if and only if the change is reported inside anyOf and the type is not newly added

[6293]

nvm we can just check path to know if it is in anyOf or not

[untitaker]

For reference I think this was fixed by #32