-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Are regex wildcards supported in path? #502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That's not supported by the spec. You can regex the value of it, but not the name itself. |
I want to regex the value. How does the spec differentiate this case with the one where only |
That wasn't what I was referring to by regexing the value. "/" is not valid in the value of a path parameter. We don't support that part of RFC 6570. See #291 (and others) for more information. |
#291 is exactly what I am looking for! PS: We have been using this for a long time by naming our path param |
This seems related to #892 |
Is
/resources/static/{subpath:*}
a valid value for the path?If yes, then what should be the name of the path param
subpath
orsubpath:*
Here is an example spec:
which fails
swagger-tools validate
with:cc @webron @wing328
The text was updated successfully, but these errors were encountered: