Issue with the Enum in arrays

[agustin-blanco]

Hi Everyone, we are using json schema and found something weird when using enums in arrays.

For the simple json schema:
{ "type": "object", "additionalProperties": false, "properties": { "example": { "type": "array", "items": [ { "type": "string", "enum": [ "1", "2" ] } ] } } }

If you put:
{
"example": ["3","1"]
}
It fails saying that 3 is not in the enum. This behaviour is correct.

But if you put something correct first, then everything else passes the validation:
{
"example": ["1","3"]
}

Sorry if this is an open issue.
Thanks!

[Relequestual]

When you use the items keyword in draft-07 or previous, and you use the array value form, it only applies the subschema value to the same index.

If you want your subschema value to apply to all items in the array, your items value should just be a single schema object.

[agustin-blanco]

Hi, thanks for the quick response.
Could you show me the workaround for this case for example?

[Relequestual]

Make the value of items be an object by removing the square brackets.

When items is an array, you're asking for the subschemas to be applied to the instance array items but only at the same index. Which is why you see the behaviour you're seeing.

I'm AFK, and while it's possible to type JSON on mobile, it's not the most fun, and I don't have much time =D

[agustin-blanco]

Thanks for your help!