Edmond/llsc 27 Data Seeding (Matching)

[EdmondLi1]

Notion ticket link

LLSC-27 Create DB Seeds

Implementation description

data seeder for the matching algorithm. Make classes orignally for the form (to make it more scalable if needed), and CLI to get the data towards the target data fromat.

NOTE: upserting the data to the DB is not complete yet; labeled todos
NOTE: this isnt being merged to main; instead its being merged to the main matching branch (aka this isnt a main-breaking pr)
NOTE: need to make sure the pdm recognizes these packages added and fast api can boot up

Steps to test

Finalized and tested the seeder. The cmd to run atm are:
cd to the backend dir and then run

python -m backend.matching.data.data_generator volunteer 10 json --file_path ~/Downloads/outputt.test

there is a CLI with approp help cmds (HERE IS FOR FILE PATH SPECIFIED)

python -m backend.matching.data.data_generator [option] [num_records] --file_path [file_path]

if no file path we can do:

python -m backend.matching.data.data_generator [option] [num_records]

What should reviewers focus on?

• coding style; formatting
• any bad practicies
• anything that wasnt pretained into the Notion Ticket

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[mslwang]

Added some comments for testing.

[mslwang]

I'd try to make this backend folder centric, or you can use local file paths .seeder.data_seeder. I can't access this from backend iirc

[mslwang]

make this a pdm script command so we can access faker and pandas packages. You can add this in backend/pyproject.toml under [tool.pdm.scripts] as matching: python3 matching/data/data_generator