Tags are breaking the structure of the Go client

[mraerino]

Tags on operations cause the Go client generator to create a package for every tag.
Although this seems reasonable we cannot use this feature because it would be a breaking change for all users of the Go client.

Current workaround is to remove tags before generating.
We need to think of a stable way to keep doing this or make a breaking change, e.g. v2 release.

[ehmicky]

Should this be closed?

[mraerino]

Let's discuss how to solve the rough edges of my workaround over here.

[ehmicky]

Three questions:

• are we always sure the Makefile will be executed on a machine that has sh (e.g. some Windows machines don't) and jq installed?
• we are already both validating and "flattening" the swagger.yml and converting it to swagger.json as part of npm run convert. This could be used instead of go-swagger validate and flatten methods?
• likewise we could remove the tags properties from that convert.js method, and output it to a second file swagger_go.json?

[verythorough]

I don't suppose that would mean we could move away from go-swagger and upgrade to OpenAPI 3.0?

[ehmicky]

While we could use the Node.js logic instead of go-swagger for validation, flattening and JSON conversion, we still need go-swagger to generate the Go SDK code.

[mraerino]

I don't suppose that would mean we could move away from go-swagger and upgrade to OpenAPI 3.0?

I'm happy to explore that. is there an existing issue?

[ehmicky]

There is an issue at #171.