[Go] Fix issues when there are more than 1 array parameters#4683
Merged
wing328 merged 1 commit intoswagger-api:masterfrom Feb 1, 2017
vvalchev:issue-4664
Merged
[Go] Fix issues when there are more than 1 array parameters#4683wing328 merged 1 commit intoswagger-api:masterfrom vvalchev:issue-4664
wing328 merged 1 commit intoswagger-api:masterfrom
vvalchev:issue-4664
Conversation
…han 1 array parameters
Contributor
|
@vvalchev thanks for the PR. I tested the update Petstore sample for Go and the result looks good. |
wing328
changed the title
davidgri
pushed a commit
to davidgri/swagger-codegen
that referenced
this pull request
May 11, 2017
… are more than 1 array parameters (swagger-api#4683)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixed issue #4664: [go] incorrect code generated, if there are more than 1 array parameters
Took the suggestion by wing328 and reworked the fix. This patch also applied to the latest master, while the original issue was about 2.2.1 code.