Closed fvanham-coveo closed 6 months ago
Thanks for the explanation and example.
This is a duplicate of
The fix is already merged to master
but hasn't been released yet.
Using your example the following is the only result.
$.group: property 'notallowed' is not defined in the schema and the schema does not allow additional properties
I think there's an unclarity with unevaluated properties in combination with subschemas, although I must admit that the json schema spec is not particularly clear on some of the details around
unevaluatedProperties
. My understanding is the following:$ref
or as separate schema's in e.g.allOf
/anyOf
) which have not passed validation.Here's a minimal sample that illustrates my case:
This schema has a two subschemas in the
allOf
, one inline one via a$ref
. Running a validation with the following inputProduces three validation errors with the latest version (1.3.2) :
The first validation error is correct, there is an extra property which should not be there. The next two are incorrect (I think):
group
should've passed validation in the firstallOf
schema, even though it hasn't been successfully evaluated in the secondallOf
schema, due to the extra property.childProp
should have passed validation in the top level schema.Looking back, earlier version (e.g. I verified with 1.1.0) do not produce the
childProp
validation error.