Can the swagger ui output utilize the web api constraints?
dellch opened this issue · 1 comments
dellch commented
The route configuration option for an HTTP triggered function accepts the following route constraints.
These don't seem to be fully supported in the swagger UI, or maybe I'm doing something wrong?
I'm attempting to use the regular expression route constraint, for example:
...
[HttpTrigger(
AuthorizationLevel.Function,
"get",
Route =
"api/test/{version:regex(^\\d+\\.\\d+)}")]
HttpRequest request,
...
Wondering if the Swagger UI can support examples? Let me know if you need more information.