Parameter Sets

[programster]

My POST and PUTS requests usually have the exact same set of parameters. However I cannot create a re-usable set, only create named parameters and then reference those over and over again. E.g. the current system works as follows

"paths": {
  "/stuff": {
    "get": {
      "description": "Gets stuff",
      "operationId": "getStuff",
      "parameters": [
        {
          "$ref": "#/parameters/param1"
        },
        {
          "$ref": "#/parameters/param2"
        }
      ]
    }
  }
}
...
    "parameters" : {
        "param1" : {
            "name": "param1",
            "description": "The blah blah blah",
            "required": false,
            "type": "integer",
            "in": "formData"
        },
        "param2" : {
            "name": "param2",
            "description": "The blah blah blah.",
            "required": false,
            "type": "integer",
            "in": "formData"
        }
    }
}

Whereas what I would really like is the following:

"paths": {
  "/stuff": {
    "get": {
      "description": "Gets stuff",
      "operationId": "getStuff",
      "parameters": [
          "$ref": "#/parameters/myParameterSet",
           {
                "name": "ExtraParameterNotInSet",
                "description": "The blah blah blah",
                "required": false,
                "type": "integer",
                "in": "formData"
           }
      ]
    }
  }
}
...
    "parameters" : {
        "myParameterSet" : [
            "param1" : {
                "name": "param1",
                "description": "The blah blah blah",
                "required": false,
                "type": "integer",
                "in": "formData"
            },
            "param2" : {
                "name": "param2",
                "description": "The blah blah blah.",
                "required": false,
                "type": "integer",
                "in": "formData"
            }
        ]
    }
}

This appears to be desired by others as well.

[webron]

Thanks for opening the ticket and making the suggestion. Proposal for spec changes should be made at the swagger-spec repository, and in fact there's already an existing ticket for this feature - https://github.com/swagger-api/swagger-spec/issues/445. Please voice your opinion there and help us evolve the spec.

[programster]

@webron sorry about that. I know now for in future. Thanks.

[webron]

@programster - that's not a problem at all, just pointing you in the right direction. We value your opinion and it helps improve the spec.