Change array items semantics

[zrzka]

Current status

Following DSL ...

properties:
  - foo:
      type: array
      items:
        - schemaA
        - schemaB

... is transformed to a JSON Schema like this one ...

{
  "properties": {
    "foo": {
      "type": "array",
      "items": [
        { schemaA },
        { schemaB }
      ]
    }
  }
}

And it says - array instance is valid if the first item validates against schemaA, second item validates against schemaB, etc.

Change

items shouldn't enforce order of items.

New semantics - an array instance is valid if every single array instance item is valid against ANY schema from items.

Transformation after change

Following DSL ...

properties:
  - foo:
      type: array
      items:
        - schemaA
        - schemaB

... is transformed to a JSON Schema like this one ...

{
  "properties": {
    "foo": {
      "type": "array",
      "items": {
        "anyOf": [
          { schemaA },
          { schemaB }
        ]
      }
    }
  }
}

Example

---
version: 1
title: WiFis
properties:
  - networks:
      type: array
      items:
        - title: WPA2 Personal
          properties:
            - ssid:
                type: string
            - password:
                type: password
        - title: WPA2 Enterprise
          properties:
            - ssid:
                type: string
            - username:
                type: string
            - password:
                type: password

Should generate a form which allows to add multiple WiFi networks where each network can be WPA2 Personal or WPA2 Enterprise.

Rendition notes

We should:

• show some + button where user can add any of these items
• every added item must show additional field like type with values WPA2 Personal & WPA2 Enterprise
• allow to change type of already existing item
  • user adds WPA2 Personal
  • user wants to change it to WPA2 Enterprise
  • when user will do it, we should try to keep as many as possible entered values
  • user already entered ssid, WPA2 Enterpise contains ssid as well, we should keep the value

Specification notes

• Add to your notes that we have to update specification with this change.

[cyplo]

The spec has been updated