The Openapi Generator for Go API and Go web app development works surprisingly well, but somehow I found that it’s not so often mentioned. Recently I’ve tried it in one of my projects, and in my (limited) experience with it, I was pleasantly surprised by how good it was. With some setup, it could generate Go code with decent quality, and it’s fairly easy to use once you get a hang of it. Whether you’re building a standalone web-app from scratch or creating a service with REST API endpoints, openapi-generator might come up handy for you.
Using a generator might save much time to kick-start your web app project. And most importantly, I found that a good, well-defined, consistent API definition is so crucial to your development, testing, and most importantly, communication among teams and customers. I highly recommend that for any sizable project, you spend some quality time on writing a good API spec. It’ll become essential to your development workflow. I used to highly doubt this, and now I don’t think I can live without it.
And if you manually keep documentation, or API specifictions in sync with your Go code, you’ll have a hard time reviewing, checking,
and testing between code and specs. The best way IMHO is to automate the process, by either generating the API code from spec, or the other around.
Many toolings support either one of these, and
openapi-generator is one of the really nice tools that I’m going to introduce in this blog post.
Openapi Generator supports many languages on the server as well as on the client side.
And it has generator for different frameworks of Go. Right here I’m going to use
as an example.
It uses the Gorilla framework for the server-side code.
For this blog post I’ve also made an example of code generation in my Github repo. I’ve generated the code,
and implemented only one endpoint
/books with example data: