You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Amend some documentation specific typoes
* Address some typoes in tests
* Amend source typo
* Fix typo in parameter call
* Pencil in contribution line
Swagger also supports the documentation of parameters passed in the header. Since grape's ```params[]``` doesn't return header parameters we can specify header parameters seperately in a block after the description.
488
+
Swagger also supports the documentation of parameters passed in the header. Since grape's ```params[]``` doesn't return header parameters we can specify header parameters separately in a block after the description.
489
489
490
490
```ruby
491
491
desc "Return super-secret information", {
@@ -955,7 +955,8 @@ The result is then something like following:
955
955
956
956
#### Changing default status codes <aname="change-status"></a>
957
957
958
-
The default status codes, one could be found (-> [status codes](lib/grape-swagger/doc_methods/status_codes.rb)) can be changed to your specific needs, to achive it, you have to change it for grape itself and for the documentation.
958
+
959
+
The default status codes, one could be found (-> [status codes](lib/grape-swagger/doc_methods/status_codes.rb)) can be changed to your specific needs, to achieve it, you have to change it for grape itself and for the documentation.
959
960
960
961
```ruby
961
962
desc 'Get a list of stuff',
@@ -1678,7 +1679,7 @@ This is how to configure the grape_swagger documentation:
1678
1679
The guard method should inject the Security Requirement Object into the endpoint's route settings (see Grape::DSL::Settings.route_setting method).
1679
1680
1680
1681
The 'oauth2 false' added to swagger_documentation is making the main Swagger endpoint protected with OAuth, i.e. the
1681
-
access_token is being retreiving from the HTTP request, but the 'false' scope is for skipping authorization and
1682
+
access_token is being retrieving from the HTTP request, but the 'false' scope is for skipping authorization and
1682
1683
showing the UI for everyone. If the scope would be set to something else, like 'oauth2 admin', for example, than the UI
1683
1684
wouldn't be displayed at all to unauthorized users.
1684
1685
@@ -1786,7 +1787,7 @@ params:
1786
1787
- store={ true | file_name.json } – save as JSON (optional)
1787
1788
- resource=resource_name – get only for this one (optional)
1788
1789
```
1789
-
For mutliversion API it creates several files with following naming: file_name_`API_VERSION`.json
1790
+
For multiversion API it creates several files with following naming: file_name_`API_VERSION`.json
0 commit comments