'oneOf' support

[tomfitzhenry]

See: http://json-schema.org/latest/json-schema-validation.html#anchor88

Example

---
swagger: "2.0"
info:
  title: oneOf
  version: 0.0.1
paths:
  /:
    get:
      summary: oneOf
      responses:
        200:
          description: word or number
          schema:
            type: object
            properties:
              aWordOrNumber:
                type: object
                oneOf:
                  - type: object
                    properties:
                      myWord:
                        title: My Word
                        type: string
                  - type: object
                    properties:
                      myNumber:
                        title: My Number
                        type: number

Expected

Either:
{"aWordOrNumber":{"myWord": "foobar"}} or
{"aWordOrNumber":{"myNumber": 1}}

Actual

{"aWordOrNumber":{}}

[mohsen1]

The schema should not have anyOf and oneOf according to Swagger specs. Swagger is designed to have predictable response objects. This helps tools like SDK generators work accurately.

[tomfitzhenry]

@mohsen1 In response definitions, is it valid to have JSON Schema (which includes oneOf and anyOf)?

[webron]

@tomfitzhenry - no. Swagger does not support JSON Schema as a whole but uses a subset of it with specific extensions. You can see what's actually supported here - https://github.com/wordnik/swagger-spec/blob/master/versions/2.0.md#schemaObject