Pantry volunteer management

[Juwang110]

ℹ️ Issue

Closes changing volunteer type for pantry volunteer assignments and serving as a hub to navigate to adding volunteers or viewing assigned pantries for each volunteer.

📝 Description

I added a volunteer management page which displays each volunteer (that's assigned to a pantry) with a column for the volunteer name, a column for assigned pantries, and a column for volunteer type. The column for assigned pantries is simply a button for each row that navigates to a nonexistent page but it would house all the pantries assigned with this volunteer. The column for volunteer type is a dropdown that allows an admin to update the type. There is a button to reset unsaved changes and a button to save current changes made in the table (volunteer type is consistent across pantry assignments so when volunteer type is changed for one user, all assignments of that user change to that new volunteer type). An add new volunteer button is also present that navigates to a nonexistent page which would allow addition/deletion of volunteers entirely. The page finally includes a search bar filter to search by name and a volunteer type checkbox filter. This page is important because it allows admins to change a volunteer's type, or navigate to add/delete volunteers, or navigate to manage a volunteer's pantries.

Briefly list the changes made to the code:

1. Added volunteer management page with ability to change volunteer type on backend
2. Backend support for assignments table
3. Volunteer type enum and new volunteer type column in assignments table

✔️ Verification

To verify my new feature worked I had to manually create a pantry and a user in PGAdmin and I added rows to the assignments table assigning users as volunteers to pantries. I then made sure saving changes to volunteer type altered every row in the assignments table with that volunteer id. I also played around to make sure the filters on the page worked just by simply changing inputs.

🏕️ (Optional) Future Work / Notes

Notes:

• RUN NEW MIGRATION to make sure your database is up to date
• Me and Fanny discussed some higher level issues with the ticket so this PR doesn't fully correspond with the ticket I got in Trello, I made some edit notes on that ticket as well.
• Add new volunteer goes to unexisting route
• View assigned pantries goes to unexisting route but it includes the volunteer_id in the url to be used to filter pantries to only ones for this volunteer

[fanzzz368]

typo for assignmentsModule (assignemnts instead of assignments)

[fanzzz368]

we can just leave the updated role as lowercase in the backend so we can get rid of upperCaseRole here

[fanzzz368]

maybe it would be good to include both the volunteer's first and last name on this line

[fanzzz368]

Here the volunteerType is shown as what we have in the backend (lowercase with _) but we probably want to display it differently in the frontend; we could do something like

const VOLUNTEER_TYPES: Record<string, string> = {
LEAD_VOLUNTEER: 'Lead Volunteer',
STANDARD_VOLUNTEER: 'Standard Volunteer',
NON_PANTRY_VOLUNTEER: 'Non-Pantry Volunteer',
};

and then here, we would do {VOLUNTEER_TYPES[volunteerType.toUpperCase()] || volunteerType} instead of {volunteerType}

[fanzzz368]

if we decide to go with const VOLUNTEER_TYPES from below, we can replace lines 102-108 with {Object.entries(VOLUNTEER_TYPES).map(([value, label]) => (

{label}

))}

so we can stay consistent with the formatting