ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Seeder: Command for scaled seeding
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
As the platform expands with more features and tables, we need to continuously update the seeder files. This leads to challenges in testing new features and changes locally, especially at scale.
we are using this command to seed database with basic data
uv run python -m app.seed_data.seed_data
so we should add another such command to populate the db with larger set of records
Describe the solution you'd like
- Introduce a command like
seed scale 500to populate data with seed data. - Ensure that this functionality supports testing from both backend and frontend perspectives.
- Facilitate local testing when new features are introduced or modifications are made
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing app.seed_data.seed_data module and running uv run python -m app.seed_data.seed_data to understand the current seed flow. Trace how records are created and determine where a scale argument can be exposed. Done means a command such as seed scale 500 populates a larger local dataset suitable for backend and frontend testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100