spec VS swag

I'm trying to use these packages to parse out a v2 open-api yaml spec file, ie to load the file, have my app read it and then to access different levels in the hierarchy of the file for validation. I was wondering if anyone had any good tutorial series or guides which can be me better understand how to implement and use these packages. I've been reading them over for a few hours, but have been getting stuck and confused as I try using them in my app. I'm not at liberty to share the code, but was hoping someone could help point me in the right direction. https://github.com/go-openapi/spec is the main package However there seems to be several other packages which build off it https://github.com/go-openapi/loads https://github.com/go-openapi/validate https://github.com/go-openapi/analysis

chai uses swaggo/swag and spec for the generation of the swaggo spec. Both of those only work with swagger 2.0 at the moment. What should be possible is to generate swagger 2.0 and then convert it to swagger 3.0, but I guess it won't be possible to use all of the swagger 3.0 features this way.

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.