SchemaGenerator and path parameter converters

[Kludex]

Discussed in #1645

^{Originally posted by jvail May 23, 2022}
Hi,

if I use type converters in a route definition ('/somepath/{parameter:int}') and generate an openAPI schema then I'd expect that the type, the converter is stripped from the URL template. But currently i get

"paths": {
        "//somepath/{parameter:int}": {}
}

instead of

"paths": {
        "//somepath/{parameter}": {}
}

Is that by purpose?
If so the parameter names inside the doc string don't match anymore if parsed e.g. inside postman. Postman would create a parameter named "parameter:int" instead of just "parameter".

Thank you
Jan

[Kludex]

• Duplicated: Endpoint path parameters type specification compatibility with OAS #746