"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.

[SereneAnt]

Wrong repo.

[awwright]

@SereneAnt Just a heads up that language is a tad bit confusing, the language seems to only apply for "items", "additionalItems" should still be able to fail even if "items" isn't defined. If in doubt check the behavior against the official test suite. If it's all too confusing, please let us know.

[epoberezkin]

@awwright:

"additionalItems" should still be able to fail even if "items" isn't defined

there is no test for such scenario in the test suite you are referring to. The draft says in clear terms that additionalItems are only taken into account when items is array.

[handrews]

The draft says in clear terms that additionalItems are only taken into account when items is array.

Also important is this line in "items":

If absent, it can be considered present with an empty schema.

This means that "items" is effectively always defined, so "additionalItems" cannot be applied unless "items" is an array of schemas. The default empty schema value of "items" takes precedence.

[handrews]

I'd say, array of schemas. If it is a schema, additionaltems is ignored.

Oops, that was a typo, I'll edit it.