Skip to content

Conversation

@antihax
Copy link
Contributor

@antihax antihax commented Dec 16, 2016

PR checklist

  • Read the contribution guildelines.
  • Ran the shell/batch script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates)
  • Filed the PR against the correct branch: master for non-breaking changes and 2.3.0 branch for breaking (non-backward compatible) changes.

Description of the PR

Add optional parameters to go client using map[string]interface{}
Add concurrency test.

Refactor tests to new API and add concurrency test.
The pet-store does not create this scenario.

Note: Optional parameters are passed through a map[string]interface{}
{{/hasOptionalParams}}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can do it one step further by providing code samples similar to what we've done for other languages (e.g. C#, Python, etc)

@wing328
Copy link
Contributor

wing328 commented Dec 20, 2016

@antihax thanks for the PR. The change looks very good 👍

@wing328 wing328 merged commit 774dd33 into swagger-api:2.3.0 Dec 20, 2016
@wing328 wing328 modified the milestones: v2.3.0, v2.2.2 Dec 20, 2016
@wing328 wing328 changed the title Add optional parameters to go client using map[string]interface{} [Go] Add optional parameters to go client using map[string]interface{} Mar 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants