Conversation
…ags, separated volunteer type and event tags
…ilters when filters are applied
navyaa31
left a comment
There was a problem hiding this comment.
I left a couple comments. One other thing is that "new" and "returning" are lower case rn but could you make them uppercase to match the other tags. Could you send screenshots to the designers and get their feedback as well?
| <span>Tags</span> | ||
| <span>Status</span> | ||
| <span> | ||
| <img src="/sort-arrow.svg" alt="" className={styles.sortIcon} /> |
There was a problem hiding this comment.
can we remove the sort arrows
There was a problem hiding this comment.
Could we have the frontend call the backend endpoints directly and remove this proxy route? you can refer to this PR where Michael removed proxies, and keep a look out for when its merged in
|
Visit the preview URL for this PR (updated for commit 38467e1): https://home-start-80e0a--pr27-feat-tag-filter-type-rkzo3osk.web.app (expires Tue, 21 Apr 2026 18:33:58 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 2d310071333235bae3893f27fc89786faff3470f |
navyaa31
left a comment
There was a problem hiding this comment.
looks good! I just left comments about a couple minor changes
| export const metadata: Metadata = { | ||
| title: "Home Start", | ||
| description: "Home Start dashboard", | ||
| title: "Create Next App", |
There was a problem hiding this comment.
Can we change this back to "Home Start" and the description to "Home Start dashboard"
| {hasSearch && ( | ||
| <div className={styles.inputField}> | ||
| <span className={styles.ic_search}> | ||
| <img src="/Union.svg" alt="Union logo" className={styles.union} /> |
There was a problem hiding this comment.
Can we use Image instead of img? I think if you just change it back to how we used Image before, it should be good
There was a problem hiding this comment.
Also can you move everything in app/components to /components. Currently there are two components folders so we are moving everything in app/components to /components
| const [volunteerData, tagData] = await Promise.all([fetchVolunteers(), fetchTags()]); | ||
| setVolunteers(volunteerData); | ||
| setTags(tagData); | ||
| console.log("raw tag data", tagData); |
There was a problem hiding this comment.
I don't think we need this after we are done with debugging
| email: string; | ||
| phoneNumber: string; | ||
| tags: VolunteerTag[]; | ||
| status: string; |
There was a problem hiding this comment.
maybe we can tighten status typing to "new" | "returning" instead of plain string
siwenshao
left a comment
There was a problem hiding this comment.
Navyaa covered most of the must-fix, I left a couple nit comments. Otherwise, the rest looks good to me!
CharlieSuarezRobles
left a comment
There was a problem hiding this comment.
Everything looks good to me and works fine on my side.
…ome-Start into feat/tag-filter-types merge.

Changes
Testing
Tested with dummy data
How to test:
Run backend and frontend as normal. Use the team database, which has dummy data matching the new schemas.
Open http://localhost:3000/volunteers and apply any tags from the tab filter buttons.
Note: you may need to log out and log back in first. Then navigate to the volunteers page.
Confirmation of Change