swagger v2 tag feature implemented #344
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
updated and corrected the grouping |
|
This still needs to pass the build and be squashed, please. |
| @@ -28,7 +28,7 @@ def content_types_for(target_class) | |||
| # swagger spec2.0 related parts | |||
| # | |||
| # required keys for SwaggerObject | |||
| def swagger_object(info, target_class, request, options) | |||
| def swagger_object(info, target_class, request, options, namespace_routes_array) | |||
There was a problem hiding this comment.
Why wound't the namespace_routes_array be passed with options?
Merge branch 'swagger-2.0' into feature/swagger_v2_namespace_tagging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Name-spcae based grouping in swagger doc V2.0
Before Change
After Change
After Change Corrected
