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 optional path segments, such as:
get 'photos(/:id)'
would match both photos/:id and photos paths.
photos/:id
photos
However, grape-swagger does not recognise these optional path segments. For example:
grape-swagger
would generate:
"paths": { "/api/v2/photos(/{id})": { "get": { ... "parameters": [ { "in": "path", "name": "id" ... } }
instead of the expected:
"paths": { "/api/v2/photos": { "get": { ... } ... "/api/v2/photos/{id}": { "get": { ... "parameters": [ { "in": "path", "name": "id" ... } }
grape-swagger should also handle Rails optional path segments in a predictable manner.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Ruby on Rails supports optional path segments, such as:
would match both
photos/:id
andphotos
paths.However,
grape-swagger
does not recognise these optional path segments. For example:would generate:
instead of the expected:
grape-swagger
should also handle Rails optional path segments in a predictable manner.The text was updated successfully, but these errors were encountered: