Better interpretation of schema in parameter list

[FabianScheidt]

In the original implementation types that are referenced using the schema attribute were only recognised if the schema referenced to a class. Otherwise the type would have have been an empty string which caused compiler errors.

I modified to code to support the following definitions:

{
    "in": "body",
    "name": "foo",
    "description": "foo",
    "required": true,
    "schema": {
        "type": "string"
    }
}

and

{
    "in": "body",
    "name": "bar",
    "description": "bar",
    "required": true,
    "schema": {
        "type": "array",
        "items": {
            "$ref": "#/definitions/FooObj"
        }
    }
}

If no type can be found it will also be set to any to avoid compiler errors.

[FabianScheidt]

I made two more changes:

• Optional parameters are now marked as optional in the typescript signature
• OPTIONS and PATCH requests can now also be executed