Flask-AppBuilder VS fastapi-crudrouter

This one might be interesting as well: https://github.com/dpgaspar/Flask-AppBuilder

I have spent a ton of time and did a TON of debugging on this. In the interest of my time and not copying information, I have put all the debugging, as well as more information on the issue, on FAB's github page. Here is the link to that to learn more: https://github.com/dpgaspar/Flask-AppBuilder/issues/1957

There's the Flask-Security extension for example. Or the Flask-Appbuilder framework, which does a whole lot more.

You can also try FlaskAppbuilder: https://github.com/dpgaspar/Flask-AppBuilder. Some of the large project like Apache Airflow, Apache Superset are built on top of it.

FastAPI does have an equivalent. Something like this? https://github.com/awtkns/fastapi-crudrouter

I can't show any pics cuz of uk NDA and all that. I can tell you the gist of it though. FastAPI is already pretty good at the abstraction part. Our middleware had a lot of rerouting and it was basically just a bunch of redundant functions. I just used this cool ass package https://fastapi-crudrouter.awtkns.com/ and used the partial function from functools to generate endpoints for every scenario/db tables.

Thanks, that's a really helpful example.

Where I think this could be taken to the next level of reusability is in modularising the front-end into API-specific components. For example, the login behaviour could depend on FastAPI-Users, with a sibling frontend library containing components that implement the same login flow. Adding user behaviour is then a matter of using the same third-party library on the front and back end.

This approach could be extended to other components such as an admin panel (perhaps using https://github.com/awtkns/fastapi-crudrouter), or a blogging component.