"additionalItems" should not be honored if "items" is an object.

[SereneAnt]

As per json-schema specification:

if "items" is not present, or its value is an object, validation of the instance always succeeds, regardless of the value of "additionalItems";

Currently (v 4.0.x), CollectionConstraint makes an extra checks for "additionalItems" if "items" is object and fails validation

[shmax]

Feel free to open a PR

[erayd]

@SereneAnt @shmax Are either of you guys intending to address this, or should I add it to my list?

[erayd]

(Note that I don't consider this a high priority, so if it goes on my list, it may take me a while to get to it).

[SereneAnt]

@erayd I'm off this train as for now, sorry. For sure, you'll do it better!

[shmax]

@erayd I wasn't planning on it, but you've been doing most of the heavy labor around here lately, so if you would like me to look at it I will.

[erayd]

@shmax Feel free if you're in the mood, but no pressure and no rush - this issue is IMO minor, has already been open for five months, and the OP doesn't seem to care.

If you don't feel like doing this, it's not an issue, and I'll probably catch is sometime during my implementation of strict-mode, once we have the rules thing sorted.

[DannyvdSluijs]

Unable to reproduce, closing for now. @SereneAnt feel free to reopen with additional information.
Also glancing at the Bowtie report the test case which seems to be the context you're describing passes (on the V6.0..0 version).