|
|
|
|
|
|
by jamal-kumar
464 days ago
|
|
|
It depends on the framework and other stuff around it but you're right about the API documentation issue, there's godoc if you want to document functions but for something like API endpoints it's not what you'd find from openapi/swagger unless whatever you're using is adaptable to that and then whenever I was working with it an older spec of it too. Always fun to run into a client who expects this from working with most of their people and you're just drooling like a gopher at them but for now if you're writing something in go for pure performance I'm not 100 on what balances best between that and auto spec... Definitely choose an API framework in go that works out of the box for that if it's important. This may be better than when I tried it a couple years back https://github.com/swaggo/swag And this one seems to generate documentation from code rather than annotations/comments etc https://github.com/go-fuego/fuego |
|
|