Before writing github.com/savaki/swag, I gave goswagger a try. I think
goswagger is a fantastic library with lots of useful features. However,
for my own use, I found things like:
var findTodos = runtime.OperationHandlerFunc(func(params interface{})
(interface{}, error) {
log.Println("received 'findTodos'")
log.Printf("%#v\n", params)
return items, nil})
a little cumbersome. I also wanted to be able to use automatic code reload
tools like https://github.com/codegangsta/gin and code generation made that
a little more problematic.
Hence was born:
https://github.com/savaki/swag
M
On Monday, March 27, 2017 at 11:39:48 AM UTC-7, Johann Höchtl wrote:
>
> The last time I used it swagger was called swagger.
>
> Lots has changed since it's OpenAPI. A huge framework evolved around it
> https://goswagger.io/
>
> I really like the approach of defining the API entirely dynamically in
> code (and announcements like
> https://groups.google.com/forum/#!topic/golang-nuts/3ebgsgF6W2c, nice!) .
> Unless I misunderstand goswagger.io, nothing prevents the drifting apart
> of the generated code from the YML - api spec.
>
> There is also an example to dynamically generate the swagger spec using
> goswagger.io
> https://goswagger.io/tutorial/dynamic.html
> and I wonder if there is experience using that. Especially is it in
> feature parity with the go generate approach of goswagger.io?
>
> Thank you!
>
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
