go-swagger toolkit

Swagger 2.0 describes your API's for you, so you don't have to

Generate a swagger spec

guide

Based on the work from https://github.com/yvasiyarov/swagger It uses a similar approach but with expanded annotations and it produces a swagger 2.0 spec. The goal of the syntax is to make it look as a natural part of the documentation for the application code. The generator is passed a base path (defaults to current) and tries to extract a go package path from that. Once it has a go package path it will scan the package recursively, skipping the Godeps, files ending in test.go and directories that start with an underscore, it also skips file system entries that start with a dot.

14 Nov 2015