fastapi-crudrouter VS starlite

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.

For the past one and a half years 😁. Checkout our docs https://starliteproject.dev/

#1286 is the issue tracking the removal of our last internal Pydantic datastructure, and PR #1382 has the addition of attrs based signature modelling. Once those are merged you will be able to use Starlite without Pydantic.

You can go to Open an Issue and open an issue for a feature request/enhancement and describe basically the behavior you are wanting to see.

Falcon FastAPI Sanic Starlite (disclosure: I do work here)

for server side , starliteproject.dev/, only python async framwork worth looking into.

Well, I'm not objective but I'd say Starlite (https://github.com/starlite-api/starlite) is a might fine codebase. You can also learn a lot about tooling and typing going through it.

I have mentioned your concerns to the Starlite discussions board - https://github.com/starlite-api/starlite/discussions/1183

You can find the complete changelog on our v1.51.0 GitHub release page.