grape-swagger
https://github.com/ruby-grape/grape-swagger
Ruby
Add OAPI/swagger v2.0 compliant documentation to your grape API
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
1 Subscribers
Add a CodeTriage badge to grape-swagger
Help out
- Issues
- Four route reads have no reader on Grape's side: success, failure, default_response, desc
- Bug Report: `default` for array params (`type: [String]`) is incorrectly placed inside `items`
- Bug report: omitted array parameters with `array_use_braces: true`
- Add support for procs in default value
- Fix issue where array params are sometimes omitted when `array_use_braces` is true
- Add OpenAPI 3.0/3.1 support with backward-compatible architecture
- [WIP] Open api3 rebased
- Wrong route ordering
- Allow range be Float
- Add default_route_visibility to Defaults
- Docs
- Liquid::Drops::Provider#multiple_services_allowed?
- Liquid::Drops::Provider#multiple_applications_allowed?
- Liquid::Drops::Provider#telephone_number
- ThreeScale::SpamProtection::Checks::Base#fail
- ThreeScale::SpamProtection::Checks::Base#invalid?
- ThreeScale::SpamProtection::Checks::Base#apply!
- ThreeScale::SpamProtection::Checks::Base#name
- ThreeScale::SpamProtection::Checks::Base#initialize
- ThreeScale::SpamProtection::Checks::Base#config
- Events::Importers::FirstTrafficImporter#notify_segment