Seed additional data

[rrabinovitch]

• applicants
• skills
• values
• applicant_skills
• applicant_values
• messages

https://github.com/HireUp-Turing/HireUp_frontend/blob/master/src/assets/test-values-skills.tsx

[GreysonElkins]

Do applicant_skills and applicant_values need their own seeds or are they built from the applicant data?

I can handle making applicants with POSTs so we don't need to seed that.

I don't know if it's worth seeding messages either, I don't think we'll be able to demo seeded messages very easily with auth, but we can run through that functionality

[rrabinovitch]

@GreysonElkins hmm good q. If you're creating applicants via the POST applicants endpoint including skills and attributes, then the applicant_skills and applicant_values join table records will be created via that POST request. If applicants are being created in the manage.py file like you just did for values and skills, then the join table records do need to be created manually. It sounded like you're doing the former, yea?

and yea, I think we can leave messages on the list for now and see where we get in the next few days with the messages functionality and then confirm whether we'll skip seeding those