grape-swagger icon indicating copy to clipboard operation
grape-swagger copied to clipboard

Add OAPI/swagger v2.0 compliant documentation to your grape API

Results 136 grape-swagger issues
Sort by recently updated
recently updated
newest added

Hello, I have this scenario: - I have an existing Grape endpoint that's something like `GET /user/:id/settings` that is consumed by a UI - The endpoint presents some entity that...

After updating to 1.5.0, it started throwing this error: ``` Error: Error opening file "/home/runner/work/api/api/swagger_doc.json" ENOENT: no such file or directory, open '/home/runner/work/api/api/swagger_doc.json' ``` Rolling back to previous version

Example grape resource: ```ruby class MyResource < Grape::API resource :my_resource do desc 'My Resource' do params MyResourceEntity.documentation success model: MyResourceEntity end .... end end class MyResourceEntity < Grape::Entity expose :my_resource_id,...

This restores the route ordering which was changed in #631. Fixes #679

Unable to hide unwanted resources. It loads all resources with all endpoints in JSON format (which later converted to swaggrUI by grape-swagger). There is no control over how swagger_doc is...

After this [pull request](https://github.com/ruby-grape/grape-swagger/pull/631) has been merged, grape swagger shows operations in reverse order from the order they were defined. I think it makes browsing the documentation a bit more...

Hi everyone, I would like to change the response type from JSON to yaml. I try config produces: ['application/yaml'] but seem not affected. I could respond yaml syntax, but the...

Sorry guys, maybe I missed something important in the docs. As I understood I should just add gem to a Gemfile, then add `add_swagger_documentation` method to my API class which...

Hello, Thank you for your amazing work! We started using grape in 2020 and man - is this a breath of fresh RESTful air after working with other ruby frameworks!...

I'm looking to protect the swagger documentation so that it isn't publicly accessible. Any suggestions on how to either add authentication or prevent the `my_api/swagger_doc` documentation from being served up...