@match_info_schema results in swagger parameter entries for both "path" and "match_info"

[waweber]

If you set up a schema that validates a route's match_info, the Swagger output will have a generated parameter description for both the parameters in the path and the ones in the schema.

Example, with a route that must have a customer_id that is a valid UUID:

class CustomerIdSchema(Schema):
    customer_id = fields.UUID(required=True)

@docs(...)
@routes.get("/customers/{customer_id}")
@match_info_schema(CustomerIdSchema)
async def route(request):
    customer_id = request.match_info["customer_id"]
    ...

The resulting Swagger schema will have a parameters property that looks like this:

"parameters": [
          {
            "in": "match_info",
            "name": "customer_id",
            "required": true,
            "type": "string",
            "format": "uuid"
          },
          {
            "in": "path",
            "name": "customer_id",
            "required": true,
            "type": "string"
          }
        ],

It contains both the customer_id from the route path as well as from the schema. In the Swagger page it would ask you to enter both.

I think specifying match_info_schema should replace these parameters, right?

[waweber]

Follow up: doing
@request_schema(CustomerIdSchema, locations=["path"], put_into="path") results in expected behavior

Edit: When I say "expected behavior" I mean it shows up in the schema appropriately; this does not also result in the proper parsing behavior in aiohttp

[maximdanilchenko]

@waweber hi! #73 opened by @maksimvrs fixes it. But @maksimvrs doesn't answer for my question about this PR. So I think I will close it by myself soon.

[lafrech]

See marshmallow-code/apispec#517.

And please comment on marshmallow-code/apispec#587 if you have any insight.

[maximdanilchenko]

Closed with #115