-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
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
Adding version to path only possible via configuration key 'version'? #403
Comments
Yes definitely. This is probably something that was added recently by @LeFnord. Thanks for contributing! |
thanks for pointing … |
have a look on it … #405 |
corrected behaviour:
this could be confusing, but I think the intention of that is, one have a gem/engine, where the API would be implemented, this could be a semantic version, and should also be documented … |
the add_swagger_documentation version should be in the upgrade guide as it used to be api_version. |
@BaneOfSerenity I think you make a good point, would you please contribute? |
@dblock would be glad to, i should have something by the end of the day. ^.^ |
This is for
grape-swagger (0.20.2)
.Not sure if this is a bug or an undocumented configuration option, but I am unable to get the version to correctly appear in the JSON file under 'paths' unless I do the following:
This will produce:
The configuration instructions in README.md lists
api_version
as a configuration option, but notversion
. This is clearly the intended behavior as shown here:grape-swagger/lib/grape-swagger/doc_methods/path_string.rb
Line 16 in 7913a9e
and in tests here:
https://github.com/ruby-grape/grape-swagger/blob/master/spec/lib/path_string_spec.rb
Should the documentation be updated to reflect this?
The text was updated successfully, but these errors were encountered: