drf-spectacular VS flask-restx

Hi, while that is the case, same can be done with drf using drf-spectacular

I would suggest drf-spectacular instead because https://github.com/axnsan12/drf-yasg#openapi-30-note

Here is your answer: drf_spectacular

If you roll your own thing, you will probably just end up re-implementing a crappy version of something that already exists. Plus, you'll miss out on really nice utilities like this one.

Generate OpenAPI3 schema for error responses using drf-spectacular: No API is complete without proper documentation. This is work in progress (PR1 and PR2). Most of it is done, but I still need to add tests and documentation. Hopefully, that will be done over the next few week(end)s. But, if you want to get a glimpse on the expected result, here’s a screenshot of a test endpoint using swagger UI.

drf-yasg - generates schema for django application - GitHub - axnsan12/drf-yasg

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: