flask-restx VS swag

When it comes to Flask, in particular, there’re plenty of choices. And in fairness, not all frameworks are created equal. You’ve got flasgger, restx (successor of flask-restplus), flask-RESTful, and flask-smorest, to mention a few. How do you choose among those???

Flask-RESTX is an extension that adds support for quickly building REST APIs - GitHub - python-restx/flask-restx

Dependendo da linguagem, existem algumas ferramentas que auxiliam na geração automática das docs do Swagger. Por exemplo, no Python+flask existe o flask-restx

However, after following [the example](https://github.com/python-restx/flask-restx/tree/88497ced96674916403fa7829de693eaa3485a08/examples/zoo_app), [more complex tutorials](https://github.com/TheMorpheus407/Tutorials/tree/master/Flask/RestplusAPI) or other [basic tutorials](https://blog.ordix.de/rest), I still only receive 404s when calling get on /api or the endpoints I tried to define.

I have a flask app which is a REST API endpoint built using flask-restx. The APIs are organized neatly using namespaces. I now need to add a new set of API to access mysql data and flask-rest-jsonapi seems to be good fit for it. However I would like to add these new APIs implemented inside a flask-restx namespace.

But if you are using a Flask based app, I recently tried Flask-RESTX library which includes some great features:

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.