pydantic-factories VS FastAPI-template

Last but not least, we moved pydantic-factories from my GitHub namespace (Goldziher) into the starlite-api GitHub organization, so its now an official package of the org.

I'm the author and sole maintainer of a library called pydantic-factories.

You can see the docs here.

Here is the link: https://github.com/Goldziher/pydantic-factories

I'm glad to say pydantic-factories is now at v1.0.0 and includes support for pydantic v1.9.0+.

So - some of you perhaps read my previous post regarding pydantic-factories, but for those who didn't- its a python package that allows you to generate mock data for your pydantic models and dataclasses. It also works for vanilla python dataclasses, so its actually not only for pydantic.

looking at your badges - i don't care your "docs" pipeline is passing, what I am not seeing is test coverage. I suggest you checkout integrating sonar-cloud with your github repository. You can see how this looks here: https://github.com/Goldziher/pydantic-factories

Here is a link to the repository - https://github.com/Goldziher/pydantic-factories, I would of course love getting more stars. But I would especially love getting more users and contributors - really do feel free to add PRs, write issues and suggestions etc.

I'm pretty partial to s3rius's template boiler plate. Used it while contracting a while back and it just tackled everything I'd want for the first few months leaving me time to focus on CRUD / business logic instead of Devops stuff. Do wish it used ruff but that was an ultra easy swap.

I found myself rebuilding a lot of basic stuff such as sign up, login, async database functionality and unit tests every time I wanted to quickly POC something. Now I like to keep things simple and customisable when starting and thus usually don't opt for using one of the already existing templates (such as this great generator: https://github.com/s3rius/FastAPI-template) since I feel I spend more time cutting stuff out I don't need.