We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ruby on Rails supports wildcard segments, such as:
get 'books/*section/:title'
would match books/some/section/last-words-a-memoir with params[:section] equals 'some/section', and params[:title] equals 'last-words-a-memoir'.
However, grape-swagger does not recognise these wildcard segments as path parameters. For example:
grape-swagger
would generate:
"paths": { "/api/v2/books/*section/{title}": { "get": { ... "parameters": [ { "in": "query", "name": "*section" ... } }
instead of the expected:
"paths": { "/api/v2/books/{section}/{title}": { "get": { ... "parameters": [ { "in": "path", "name": "section" ... } }
grape-swagger should also recognise wildcard segments as path parameters.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Ruby on Rails supports wildcard segments, such as:
would match books/some/section/last-words-a-memoir with params[:section] equals 'some/section', and params[:title] equals 'last-words-a-memoir'.
However,
grape-swagger
does not recognise these wildcard segments as path parameters. For example:would generate:
instead of the expected:
grape-swagger
should also recognise wildcard segments as path parameters.The text was updated successfully, but these errors were encountered: