Just fyi here is the documentation on the expectation of overriding types like you have.

Also it should be defined as a child of the implicit params collection

@ApiImplicitParams({
    @ApiImplicitParam(name = "status_ids", required = false, allowMultiple = true, paramType = "query", dataType = "array")
})

Thank you for quick response,
I'm using @ApiImplicitParam as a child of @ApiImplicitParams.

What i need is to describe all possible query parameters, where one of the parameters is an array.

@ApiImplicitParams({
            @ApiImplicitParam(name = "app_id", required = false, dataType = "string", paramType = "query"),
            @ApiImplicitParam(name = "status_ids", required = false, allowMultiple = true, paramType = "query", dataType = "array"),
            @ApiImplicitParam(name = "limit", required = false, dataType = "int", paramType = "query")
    })
    @RequestMapping(method = GET)
    public List<App> listApps(@ApiIgnore HttpServletRequest request, @ApiIgnore HttpSession httpSession) {
        String query = request.getQueryString();
        //some code here
    }

My question is: what dataType value should i use for implicit parameter to be resolved into "array" type.

Change allowMultiple = true, paramType = "query", dataType = "array" to allowMultiple = true, paramType = "query", dataType = "string".

dataType as descibed in the link ☝️ the value should be able to resolve to a valid type in the ClassLoader

I apologize for reopening this issue (didn't want to create a duplicate one).

Based on the swagger specification, one of the allowed types for a query parameter is "array". However, I can't seem to set this for an array of enums through the @ApiImplicitParam annotation for an object annotated with @ModelAttribute:

@ApiImplicitParams({
    @ApiImplicitParam(name = "classifications", allowMultiple = true, paramType = "query", allowableValues = "ONE, TWO, THREE")
})

This seems to generate a swagger model with the type set to "ref". As originally mentioned in this issue, I can't set the type to "array" because dataType needs to be a class that can be instantiated. I did set the type to "string", but this simply sets dataType to "string", and there is no "items" entry even though allowMultiple is true. I basically end up with this:

{
    "enum": [
        "ONE",
        "TWO",
        "THREE"
    ],
    "in": "query",
    "name": "classifications",
    "required": false,
    "type": "string"
}

The enum itself is called Classification, and the type of the classifications field within the @ModelAttribute-annotated class is Classification[].

I tried adding rules (using resolver.arrayType) to resolve arrays of type Classification to arrays of type String, but I still end up with ref. Removing the @ApiImplicitParams annotation completely ends up giving me this:

{
    "name": "classifications",
    "in": "query",
    "required": false,
    "type": "array",
    "items": {
        "$ref": "#/definitions/"
    },
    "collectionFormat": "multi"
}

But this doesn't have the list of enum values or the item type I want ("string"). What is the correct way to accomplish this?

@vivin I fixed a subtle bug with it, but it should be available when we release 2.4.0. details in the commit ☝️ Thanks for reporting!

@dilipkrish Thanks Dilip!

@dilipkrish One more question - I can't seem to find 2.4.x snapshot versions on the snapshot repo. Am I looking in the right place? Or should I try building directly from the source?

Haven't upped the version yet. So u should find it @ 2.3.2-Snapshot. Details on how to get it it at http://springfox.io

@dilipkrish Thank you!

strange results for Pojos:

• swagger produces cool Model Schema for Data Type if @ApiParam(hidden=false) is applied
• swagger produces ordinary string for Data Type if @ApiParam(hidden=true) and @ApiImplicitParam(name = "user", value = "user", required = true, dataType = "User") is applied
  How can I configure Swagger to produce Model Schema (not ordinary string!) ?

I wanted to do the same using openapi 3. but there is no allowMultiple = true.
Any Idea how to get the same things done in open api 3.