Ddb/ssf 8 admin order management frontend

[dburkhart07]

ℹ️ Issue

Closes #8

📝 Description

Write a short summary of what you added. Why is it important? Any member of C4C should be able to read this and understand your contribution -- not just your team members.

I followed the Figma for the admin order management frontend page. I needed to add a few things in particular such as a slight adjustment to the backend in order to get the SSF pantry representative (the volunteer the admin assigns to the order). Aside from that, a majority of the ticket was a similar design pattern to the admin donation management page.

✔️ Verification

Verified proper UI according to Figma:

🏕️ (Optional) Future Work / Notes

• The colors are completely random from a set of 4. Later on we will need to assign each user a color for this perhaps
• The statuses are hardcoded as well (we assume we only have 3 with those specific values). This will likely not change much but, if it does, there will need to be changes here.

[amywng]

LGTM

[sam-schu]

Some initial things I noticed:

1. Have you checked with Priya whether we want to display the statuses as we're currently keeping track of them internally, or with the names they have in the Figma?
2. Can you check with Priya if "Assignee" should be changed to "Assignees"?
3. Can you check with Priya what the page should look like if there's no orders? To me when there's no orders it looks like the page didn't load properly (even though it did)
4. If there are no orders, hovering over the right pagination chevron causes it to change color, even though there is only one page
5. Can we make it so when you hover over an enabled chevron, the cursor also changes to a pointer?
6. Can we cycle through the assignee colors rather than having them be randomly assigned? It looks weird to me when we get the same color twice in a row, and it also feels weird that refreshing the page changes all the colors

[amywng]

lgtm!!! 😎 🤏 🕶️ 😮‍💨

[sam-schu]

1. Currently, filter and sort act only within the current page, which I assume is not the intended behavior for the design. You can check with Priya, but I assume they should filter and sort across all orders in the table, regardless of which are currently displayed
2. Nit: Could the assignee colors be assigned when the orders are fetched, based on the sequence they will initially be shown in the table, and then kept the same (i.e., the same order gets the same color) regardless of any filtering/sorting? Currently, when you change the sorting, the assignee colors don't move with the orders but instead stay the same in each row of the table, which makes it look like nothing is changing.

[sam-schu]

Unresolved a couple comments

[sam-schu]

We shouldn't be updating the yarn lock if we aren't changing the package.json

discussed over slack

[sam-schu]

Would be great if you could leave a comment with the changes you made to setFilterStates about why the comparison is necessary to avoid unnecessary pagination resets - I was confused at first until I realized that the contents of the filter search box is part of the filter states. Feel free to merge after that, looks great!