Support for Golang

[flavianh]

Is it in the backlog?

[webron]

Obviously, we can't reliably provide implementations for all existing languages since we're not proficient with everything out there. However, such contributions would be gladly accepted!

[flavianh]

Great! Do you have guidelines for such implementations? How hard is it to make one? I've checked the Python generation files, it seems like there is not so much code

[webron]

There's no code at all really, it's just mustache templates.

I think the easiest way would be to look at the current implementations - https://github.com/swagger-api/swagger-codegen/tree/master/src/main/resources

Keep in mind that most work that's done now is towards the next major version of the codegen, so it may be better to contribute to that branch - https://github.com/swagger-api/swagger-codegen/tree/develop_2.0/src/main/resources

[flavianh]

OK thanks

[webron]

No, thank you! It would be great to add support for additional languages. Feel free to ask any specific questions as you encounter them.

[fehguy]

I believe @casualjim has worked on this some already

[c4milo]

I might be willing to contribute support for Go, despite my distaste for Scala :P

[fehguy]

well, if you're working with the develop_2.0 branch, the codegen code is pure java. So you don't need to plug your nose :)

[mattolenik]

Is any of this work yet available (even if untested)? I'm on a project where this would be useful, and I'm contemplating writing Golang support for Swagger.

[fehguy]

I suggest joining forces with @casualjim who is very far along with his project.

[mattolenik]

I'd rather just implement a generator for the existing codegen, rather than write something from the ground up in Go.

Unfortunately, I've run into a problem. I'm not sure if I the codegen model supports being able to generate idiomatic Go code. What I want is to have a Go package for each version of each API, and in that package will be the code for the models and the operations. I don't want separate modules for operations and models. Models and operations need to go into the same directory, and that directory needs to be based on the operation name. For example, if I have some operation "foo" then you'd expect to see all the code under "src/my/api/foo/v1", and you'd expect each .go source file in this directory to say "package foo" at the top.

Does this make sense? Is there any way I can do this with the current codegen model? This is a good example of the structure I'm trying to mimmic: https://github.com/google/google-api-go-client

[fehguy]

Fork swagger-codegen, send me the URL and I'll send a pull request to help with the structure.