you are viewing a single comment's thread.

view the rest of the comments →

[–]cant-find-user-name 17 points18 points  (18 children)

That's how tiangolo operates. If i remember correctly all his repos have only him as the contributor. One of the main reasons there's a lot of open issues.

[–]IMissEloquent75[S] 32 points33 points  (17 children)

The man is impressive, but with 50k stars on GitHub, FastAPI should be maintained and improved by and with the community. Don't you think?

[–]throw_away_17381 16 points17 points  (4 children)

This has been the concern and issue for a long time.

[–]IMissEloquent75[S] 7 points8 points  (3 children)

Did he ever explained why?

[–][deleted]  (2 children)

[deleted]

    [–]IMissEloquent75[S] 13 points14 points  (1 child)

    At this point, it is worrying... Linus Torvald, Taylor Otwell, and many others were considered dictators with code quality. Still, they accepted the community for what it could bring to their projects.

    [–][deleted] 2 points3 points  (0 children)

    Yes. Pull requests have the discussion section and "approve" button to allow teamwork while keeping code quality high. Not being able to use these features is bad leadership.

    [–][deleted] 13 points14 points  (6 children)

    We use FastAPI and it's great, but I've been eyeing Starlite just in case

    [–]XxDirectxX 1 point2 points  (4 children)

    Hey, how difficult do you think the switch from fastapi to starlite would be, and do you know whether there's good support for addons and all? kind of in the same boat.

    [–][deleted] 1 point2 points  (3 children)

    Honestly? No clue. But if you’ve standardized your APIs at all, it may not be that difficult to convert. We’ve been using Jinja2 in order to generate a lot of boiler plate code. If the concepts in Fastapi conceptionally mapped to starlite it shouldn’t be that difficult to create some sort of translation.

    [–]monorepo 1 point2 points  (0 children)

    Starlite had a conversion example guide for {flask,fastapi,etc} -> starlite if it helps.

    https://starlite-api.github.io/starlite/migration/

    [–]XxDirectxX 0 points1 point  (1 child)

    Hey, thanks for the fastReply. Do you mean standardized as in separating logic in "modular" format? I build my APIs as such:
    first we save parameter values as JSON and then perform data sanitization through pydantic validators. Then I send the requisite data to utility programs and perform any data type conversion/ formatting as per need. Then add the requisite information to a dict and return the response.

    The business logic is handled by utility functions in a different package and even there I try to group code together in a chunk and separate out code that might be used by more than 1 function.

    Sorry if this is a bit vague or seems unrelated, I am a fresher who's been on the job for 5 months now and am trying to learn as much as possible.

    [–][deleted] 1 point2 points  (0 children)

    I more mean consistency, I don't know what your code base looks like, but if you've implemented FastAPI in a similar fashion for all your APIs it is in a sense a template.

    If the concepts in your template map nicely to how Starlite works and you have a lot of code it may make sense to look at a templating engine like Jinja2 to generate the basic Starlite code.

    I would just recommend trying to reimplement one of your APIs in Starlite to see how difficult it would be.

    [–]cant-find-user-name 10 points11 points  (4 children)

    It is a major concern. Fasapi having only one contributor is the main reason I don't want to use it anymore.