rest VS Goyave

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.

Take a look at Goyave, it is inspired by Laravel on some aspects. It's focused on REST APIs only. I wouldn't say it's "the best" because there is no best, it always depends on your needs. Anyway, yesterday I released the first preview version of the v5, a rewrite of the framework trying to solve many weak points of the previous version. It's poorly documented for now because it is still WIP and I wouldn't recommend building production applications with it. Stick to v4 for this for now.

I can't say it rivals because it's still far from that, but I'm working on Goyave. The goal is to make a complete package so you can focus on your business logic as much as possible. It's focused on REST APIs only.

You can try https://goyave.dev/ ?

Take a look at Goyave.

Check out Goyave and see if it would fit your needs.

Goyave is not widespread but it's inspired by Laravel on some aspects. Try it out!

Hey! That's the goal of Goyave, a framework I'm working on. Its creating was motivated by the same complaint you have.

I'm using Goyave, removes the hassle of setting up a lot of things yourself for bigger projects or APIs that are going to be exposed to the internet. Otherwise for internal services it's probably overkill.

Take a look at Goyave.