swag VS GoSwagger

Hey Gophers, I'm exploring Swagger generation for a REST API in Go (using go-chi). Currently, I'm testing https://github.com/swaggo/swag/, but I'm uncertain if it's the optimal solution. What are your thoughts or recommendations?

Swaggo is a tool that creates Swagger documentation for Go APIs. It makes documenting API endpoints easier, helping developers understand and use the API.

Some of the features: - ✅ Using Vertical Slice Architecture as a high level architecture - ✅ Using Event Driven Architecture on top of RabbitMQ Message Broker with a custom [Event Bus](pkg/messaging/bus/) - ✅ Using Event Sourcing in Audit Based services like [Orders Service](services/orders/) - ✅ Using CQRS Pattern and Mediator Patternon top of Go-MediatR library - ✅ Using Dependency Injection and Inversion of Controlon top of uber-go/fx library - ✅ Using RESTFul api with Echo framework and using swagger with swaggo/swag library - ✅ Using Postgres and EventStoreDB to write databases with fully supports transactions(ACID) - ✅ Using MongoDB and Elastic Search for read databases (NOSQL) - ✅ Using OpenTelemetry for collection Distributed Tracing with using Jaeger and Zipkin - ✅ Using OpenTelemetry for collection Metrics with using Prometheus and Grafana - ✅ Using Unit Test for testing small units with mocking dependent classes and using Mockery for mocking dependencies - ✅ Using End2End Test and Integration Test for testing features with all of their real dependeinces using docker containers (cleanup tests) and testcontainers-go library

[1]https://github.com/swaggo/swag/issues/386

I used this the other day and found it very easy to set up: https://github.com/swaggo/swag

I use the fizz for developing my webservices + docs, it's smooth! There is swaggo but I don`t like it because the source code get dirty (lots of comments)

You can use swaggo/swag with code annotations

checkout swaggo/swag.

Hi everyone, I was going through go-swagger todo list example and came across the following implementation of server struct.

Much or some OpenAPI tooling has not even moved past OpenAPI 2.0 some even refusing and saying that they will not update to Swagger 3.0 [0] and others have issues open since some 2019 and still open with no resolution in sight (because these are individuals doing out of passion and the spec is complex to implement) and yet we have Open API spec 4.0

All this is - trying to do RPC over HTTP in a fashion that was deemed virtuous in some doctoral thesis.

I wish there were better alternatives for RPC that work everywhere including browsers.

[0]https://github.com/go-swagger/go-swagger/issues/1122#issueco...

I recommend this: https://github.com/go-swagger/go-swagger

Hi there. I am seeking any open source Schema Driven Development tool like go-swagger, but i really need to use there:

Can anyone point out what am I doint wrong? Note: I have already checked No properties generated in json file for swagger:response but didn't find anything which can help.

Try this https://github.com/go-swagger/go-swagger. It generates code for you. It is useful if only for you to generate the models/structs you could use.

go-swagger brings to the go community a complete suite of fully-featured, high-performance, API components to work with a Swagger API: - Github - Swagger 2.0 implementation for go

There is also a Code Generator that reads in a swagger file (2.0 only) and generates code for you, so all you have to do is create functions.