Are optional keys in schema supported?

[bensleveritt]

This is a repost from API Blueprint (https://github.com/apiaryio/api-blueprint/issues/53), but they've pointed my question in the direction of Gavel, so here goes.

Does 1A support required/optional flags in schema specifications?

My specification is:

## Entities [/api/entities]
+ Model

    + Body

    {
        "entities": [
            {
                "id": "entity1",
                "name": "Entity"
            }
        ],
        "total": 1
    }
    ```

+ Schema

    ```
    {
        "title": "Entities Schema",
        "type": "object",
        "properties": {
            "entities": {
                "type": "array",
                "items": {
                    "required": ["id"]
                }
            },
            "total": {
                "type": "integer"
            }
        }
    }
    ```

Trying to validate this response with Dredd, and it says that `name` is required and is missing. I've validated the schema against http://json-schema-validator.herokuapp.com/ and it's all clear, leading me to suspect that it's how I've written the schema.

Thanks in advance.

[tomgco]

Any update on this?

[bensleveritt]

None from me, other thanks to say I've stopped trying to use schemas, instead using blank objects (which will pass the validation in general, just not the specific components).

[Almad]

Hi, sorry, this totally went through my checks. I think it looks like bug, but I'll let @netmilk to verify.

Long-term, we plan to push MSON more then schemas, but I think the underlying error will be same for both.

[bensleveritt]

Okay, after spending all day writing schemas, I now believe MSON is superior for my needs (not to mention easier/quicker).

Am I right in thinking required/optional is still not usable?

[honzajavorek]

I wasn't able to reproduce this. It looks like this is not relevant anymore. Thanks for reporting this though!