Json Schema Validation of Array or Objects

Question

I have a set of options for validation:

{
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "parsePosition Validator",
    "type": "object",
    "properties": {
        "option1": {
            "type": "array",
            "items": {
                "tpye": "number"
            },
            "minItems": 3
        },
        "option2": {
            "type": "array",
            "items": {
            "tpye": "number"
            },
            "minItems": 3
        },
        "option3": {
            "oneOf": [
            {
                "type": "array",
                "items": {
                    "tpye": "number"
                },
                "minItems": 3
            },
            {
                "x": { "type":"number" },
                "y": { "type":"number" },
                "z": { "type":"number" },
                "required": ["x","y","z"]
            }
        }
    },
    "oneOf": [
        { "required":["option1"] },
        { "required":["option2"] },
        { "required":["option3"] }
    ]
}

Essentially the input of the json can be any of the three options. My issue arises when trying to validate option3. Possible inputs could be:

{
    "option3": [1,2,3]
}

or

{
    "option3": {
        "x": 1,
        "y": 2,
        "z": 3
    }
}

However, when I use the array rather than objects, the validator does not throw an issue with an empty array or an array of incorrect size.

Am I missing something?

Relequestual · Accepted Answer · 2020-09-25 20:25:25Z

1

You are missing something very simple...

You haven't put type: object in your second subschema in the oneOf. for option 3.

The reason you need this is because JSON Schema is a constraints based language.

Specifying properties, doesn't mean the the instance location HAS to be an object; You also need to say "this location should be an object".

An array of any size is valid under your subschema oneOf[1], because properties and `required are only applicable to an object.

answered Sep 25, 2020 at 20:25

Relequestual

12.4k7 gold badges52 silver badges87 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ether Over a year ago

Also, x, y and z are specified as if they are keywords; they should be wrapped in a {"properties":{...} object.

Relequestual Over a year ago

See, it's EASY to miss basic things! =]

Collectives™ on Stack Overflow

Json Schema Validation of Array or Objects

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related