go-restful VS rest

Chech this one https://github.com/emicklei/go-restful is the one used in kube-api

I'm mainly using go-restful with the go-restful-openapi extension, mainly because it's easy and you get an openapi spec out of it.

It's not super popular, but my personal favorite is Go-restful (https://github.com/emicklei/go-restful) with Go-restful-openapi (https://github.com/emicklei/go-restful-openapi) for documenting the API in code.

Swaggest Rest can generate OpenAPI definitions from Go code, but it's not as comprehensive as Goa and does not support gRPC.

This is what I use: https://github.com/swaggest/rest

This has been the best implementation of the use case interactor I’ve seen and it outputs spec 3: https://github.com/swaggest/rest

Other times you might need a JSON REST API to generate OpenAPI docs code-first… for that I’m a fan of Swaggest REST. REST through clean arch.

For full code-first OpenAPI v3 REST, I’ve been using https://github.com/swaggest/rest and I like it.

For anything that needs OpenAPI docs, I’ve honestly found https://github.com/swaggest/rest pretty awesome. It’s basically just doc generation on top of Chi, but it does a lot of stuff right.

I used Echo for a lot of stuff (and it was easy to work with), but recently OpenAPI 3 has been a requirement, so I've switched to https://github.com/swaggest/rest

I've tried go-swagger comments to instrument existing code, but wasn't quite satisfied due to magical nature and error friendliness of those comments. So I decided to implement first-class OpenAPI generation on top of self-documenting action handlers: https://github.com/swaggest/rest/blob/master/_examples/basic/main.go. Schemas are generated from request and response structures using reflection and field tags.