Can we have a discussion about the Go code generator?

So I saw that 3.0.0 will use this repository for codegen generators. Version 2.3.x introduced some major breaking changes to the produced code. While most of these changes made sense, some of them are - in my opinion - bad choices.

I would like to use the chance that releasing 3.0.0 is, to start a discussion on providing a better code generator for Golang.

I'd like to start with some things that I think are really well done in the new 2.3.x release:

1. It's now possible to provide a custom http.Client
2. It's now possible provide a context.Context in API calls

I think there are also some issues.

1. Redirects do apparently no longer work, because all status codes higher than 299 result in an error:

	if localVarHttpResponse.StatusCode >= 300 {
		bodyBytes, _ := ioutil.ReadAll(localVarHttpResponse.Body)
		return localVarHttpResponse, reportError("Status: %v, Body: %s", localVarHttpResponse.Status, bodyBytes)
	}

2. Adding request bodies now requires passing a map[string]interface{} that needs, for example, a body key.

The second limitation is especially painful from an API point of view as type assertions are necessary to decode the payload, and the API is not very developer friendly in the context of Go. In real-world use it looks something like this:

CreateResource(context.Context, map[string]interface{}{"body": &SomeStruct{}})

I propse that instead, a type is used to solve this, for example:

type CreateResourceParameters struct {
  Body *SomeStruct
  Path ...
  Query ...
}

This would make the process of passing down request parameters much more usable and less error prone.

Let me know what you think.

Review the Go generator behavior described in the issue, especially status-code handling and map[string]interface{} request bodies. The first step is to gather maintainer direction on whether typed parameter structs and changed redirect handling are desired for 3.0.0. Done would require an agreed design, implementation scope, and validation criteria.