Inaccurate error message while using "unevaluatedProperties": False

[MLL1228]

Inaccurate error message while using "unevaluatedProperties": False

[Julian]

I have to take a closer look but just off the bat I'd recommend comparing with #1132 or #1026 it may be that's relevant.

(Again not having played with your example) I suspect what's happening has to do with the spec's behavior saying that when a subschema fails, it does not produce annotations -- specifically what that means is that if your subschema is not considering your instance fully valid (the schema in your allOf), then indeed those properties were not evaluated, so they should be considered unevaluated -- there is no "partially" evaluated.

The fact that that error isn't the one you see though is #1132 which is why I point you there.

But I can have a closer look at some point if the above doesn't help / is incorrect on closer inspection.

[ClementDelannoySlateDigital]

Hey,

I think I found the same type of issue here.

The real error was
'44100' is not of type 'number'
(this property is defined in an 'allOf' section.
But jsonschema raises an 'Unevaluated properties' with all properties defined on the 'allOf' section.

This is an important issue for me because it leads to false leads that may complexify the debugging a lot.

That would be terrible if it was a design error in the standard...

Have you been able to investigate the issue? I can help looking for something wrong in the logic, please tell me what you've found on your side!

Thanks