Well, I found that flask-restx may no longer be maintained (last commit was 10 months ago as of this post). That's too bad seeing as I spent a decent amount of time learning it and overall thought it served its purpose well. I found the community has moved to flask-smorest. What I am looking for is how people are structuring their api for modularity so it can be scaled well. flask-restx has good documentation on how to do this for multiple apis with reusable namespaces. project/ ├── app.py ├── apiv1.py ├── apiv2.py └── apis ├── __init__.py ├── namespace1.py ├── namespace2.py ├── ... └── namespaceX.py Is something like this achievable? Is there an equivalent of flask_restx.Namespace for flask-smorest? The only documentation I have found is flask-smorest Advanced Usage page which is lacking. Someone wrote an article why use flask-smorest and their comment on flask-smorest feels on point so far. The documentation is the weakest point (compared to Flask-RESTX),... I know there are other REST API library's, which I will look into, but I figured I would start with flask-smorest. Also, let me know if this question is better asked in another forum. Thanks. Continue reading...
