simplegmail VS fastapi-crudrouter

Step 2 Choosing a library. Assuming you're using Oauth you have a few libraries you can choose from. There is the official Google python library, and there are a few libraries that wrap the official one for a cleaner API. https://developers.google.com/gmail/api/quickstart/python https://github.com/jeremyephron/simplegmail Just from poking around a bit simplegmail has a nice API, but always be cautious about using 3rd party libraries when you're providing auth. Use at your own risk.

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.