#3128: Schema Changes

[wavehassman]

Changes

I added the necessary fields to the schema, and created a migration that linked reimbursement requests and projects together directly instead of going down a long rabbit hole. I also had to change the createVendor controller and service function, and bill of materials service function along with the seed data.

Notes

Even though I did a create only migration and then changed things around to make it the official one, it still made two migrations, not really sure why

Checklist

It can be helpful to check the Checks and Files changed tabs.
Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.

• All commits are tagged with the ticket number
• No linting errors / newline at end of file warnings
• All code follows repository-configured prettier formatting
• No merge conflicts
• All checks passing
• Screenshots of UI changes (see Screenshots section)
• Remove any non-applicable sections of this template
• Assign the PR to yourself
• No yarn.lock changes (unless dependencies have changed)
• Request reviewers & ping on Slack
• PR is linked to the ticket (fill in the closes line below)

Closes #3128

[walker-sean]

Looking good! Make sure to update the seed data and endpoints to work with the migration. Before that, check that the migration works on unmigrated data