Multiple types support for parameters

[buremba]

I have a parameter that can be more than one type. (Consider an endpoint that takes an arbitrary key (string) and value (string, number or boolean) parameters and store them in a database.) It seems "parameter" object requires "type" field name and the value of "type" field must be one of "string", "number", "integer", "boolean", "array" or "file". Currently, I'm stuck with this problem since there's no workaround.

[jharmn]

Link to parent #565

[jharmn]

Now that we're working to include full JSON Schema support #741, and we have schema support for parameters #654, wouldn't we be able to handle this in the schema definition?
e.g. if string or integer were allowed for a parameter:

swagger.json

...
  "parameters": [
    {
      "name": "myParameter",
      "in": "query",
      "schema": {
        "$ref": "parameterSchema.json"
      }
    }
   ]

parameterSchema.json

{
  "oneOf":
  [
    {
      "type": "string"
    },
    {
      "type": "integer"
    }
  ]
}

[webron]

This can now be done with oneOf.

[akindo]

It's described in the Inheritance and Polymorphism section of the OpenAPI documentation.