Swagger Custom Mappings not working with multiples parameters

[samirbraga]

I'm trying to document a simple Pagination object in swagger-custom-mappings.yml this way:

- type: Pagination
  required: false
  specAsParameter:
    - type: integer
      name: pageSize
    - type: integer
      name: page

But, the rendered result is it:

Looking at the code, I found this block where only the first element of specAsParameter array is really interpreted correctly with type and etc. For example, in another object, I've used a list of filters as a query string parameter, but the type array can't be placed in another position than not first.

play-swagger/core/src/main/scala/com/iheart/playSwagger/SwaggerSpecGenerator.scala

Lines 219 to 236 in 526323d

	csp.specAsParameter match {
	case head :: tail ⇒
	def withPrefix(input: JsObject): JsObject = {
	if (swaggerV3) Json.obj("schema" -> input) else input
	}
	val nullableName = if (swaggerV3) "nullable" else "x-nullable"
	val under = if (swaggerV3) __ \ "schema" else __
	val w = (
	(__ \ 'name).write[String] ~
	(__ \ 'required).write[Boolean] ~
	(under \ nullableName).writeNullable[Boolean] ~
	(under \ 'default).writeNullable[JsValue])(
	(c: CustomSwaggerParameter) ⇒ (c.name, c.required, c.nullable, c.default))
	(w.writes(csp) ++ withPrefix(head)) :: tail
	case Nil ⇒ Nil

Why this behavior?

[Javakky-pxv]

@samirbraga
We are currently reviewing it. It may take some time, but we plan to address it.