cherrybomb VS flask-restx

Standard library does not provide all solutions for Error Handling.. In fact, different errors may be returned by the same function, making it increasingly difficult to handle them precisely. Personal anecdote, in our company we developed Cherrybomb an API security tool written in Rust, and we need to re-write a good part of it to have a better errors handling.

Cherrybomb is a CLI tool that helps you avoid undefined user behavior by auditing your API specifications, validating them, and running API security tests.

If you're looking for a new way to understand and manage your API, consider using OpenAPI, and if you want to secure it consider using CherryBomb to automate your security test. Managing and Testing it's the key,now your can keep your API safe :)

You can find the code on GitHub: https://github.com/blst-security/cherrybomb

API validation is an important part of developing and releasing a new API. It helps to ensure that the API behaves as expected and that it meets all the requirements of its users. Validating an API can be made easier with automated testing tools and CI/CD integrated validation 💡 tools, but it can also be done by hand.

You can learn more about Cherrybomb and how it can help you over at its repository.

I believe that Cherrybomb will make it simpler for developers to construct application programming interfaces (APIs) that are standardized, well-documented, and straightforward to implement. We have high hopes that Cherrybomb will emerge as the industry standard for application programming interface (API) development.

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: