Skip to content

[SSF-121] Remove User ID from Routes for Current User Pages#96

Merged
amywng merged 33 commits intomainfrom
acw/SSF-121-remove-ids-from-routes
Feb 17, 2026
Merged

[SSF-121] Remove User ID from Routes for Current User Pages#96
amywng merged 33 commits intomainfrom
acw/SSF-121-remove-ids-from-routes

Conversation

@amywng
Copy link
Member

@amywng amywng commented Feb 2, 2026

ℹ️ Issue

Closes SSF-121

📝 Description

  • Removed IDs from frontend pages' routes
  • Added endpoint to get associated pantry ID of authenticated user, along with tests
  • Cleaned up request endpoints to match rest of codebase

✔️ Verification

Verified user-specific routes don't need ID params

🏕️ (Optional) Future Work / Notes

Did you notice anything ugly during the course of this ticket? Any bugs, design challenges, or unexpected behavior? Write it down so we can clean it up in a future ticket!

@amywng amywng force-pushed the acw/SSF-121-remove-ids-from-routes branch from 32ab190 to a692028 Compare February 14, 2026 14:50
Copy link
Member

@maxn990 maxn990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice Amy! A few suggestions but otherwise looks great

Comment on lines 58 to 61
} catch (error) {
console.log(error);
}
} catch (error) {
console.log(error);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

besides cleaning up the console logs, should there be any error handling in the frontend here? like should the user see anything

Copy link
Member Author

@amywng amywng Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm not going to remove it here because I can't leave the catch branch empty, but I commented about it in justin's alert pr

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good

});

if (!pantry) {
throw new NotFoundException(`Pantry for User ${userId} not found`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should add a test for this case, I may have missed it but I don't see one

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we haven't refactored the pantries service tests yet but i added one commented out for now

@Juwang110 Juwang110 self-requested a review February 15, 2026 21:45
@amywng amywng requested a review from maxn990 February 16, 2026 18:28
Copy link
Member

@maxn990 maxn990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🥇

Comment on lines 58 to 61
} catch (error) {
console.log(error);
}
} catch (error) {
console.log(error);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good

Copy link

@Juwang110 Juwang110 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks really good! Just a couple small cleanup things. As a small note, there are usages of request-form/pantryId in the delivery confirmation modal and confirmDelivery apiClient method. I think that modal and stuff needs to be refactored anyway though.

One more thing though, is there a reason why we are not updating homepage.tsx with the new routes? I think it would make sense to replace Pantry Dashboard (ID: 1) and Request Form (Pantry ID: 1). Besides that looks good!

@amywng amywng requested a review from Juwang110 February 17, 2026 17:00
Copy link

@Juwang110 Juwang110 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@amywng amywng force-pushed the acw/SSF-121-remove-ids-from-routes branch from 31d48e3 to 4593542 Compare February 17, 2026 18:26
amywng and others added 10 commits February 17, 2026 16:33
* login page

* signup page

* forgot password flow

* refactoring to use my login page instead of authenticator from amplify

* refactoring to combine verification and new password modals

* minor refactoring

* prettier

* minor refactoring

* switching button color to ssf blue

* minor refactoring

* adding password requirement info and eye crossed out icon

* changing password requirement text to be accurate

* making all routes protected, refactoring password requirement visual

* adding alert for password being 8 characters at least
@amywng amywng force-pushed the acw/SSF-121-remove-ids-from-routes branch from 4593542 to f892adc Compare February 17, 2026 22:10
@amywng amywng merged commit 6a4231b into main Feb 17, 2026
2 checks passed
@amywng amywng deleted the acw/SSF-121-remove-ids-from-routes branch February 17, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants