[JH] Restrict Route Access

[hsiangj]

Description

This code restricts route access to "List" and "Manage List" when user is not signed in. Using the <Navigate> component, user is redirected to "Home" or "/" route path to sign in.

Note: The route path to "Home" currently renders information about user's lists. This may be changed to the landing page in a future issue.

Related Issue

Closes #51
Sub-issue of #14

Acceptance Criteria

• Users who are not signed in won't be able to navigate to "List" and "Manage List" pages via navbar or directly through the URL.

Type of Changes

Use one or more labels to help your team understand the nature of the change(s) you’re proposing. E.g., bug fix or enhancement are common ones.

Updates

Before

Successfully navigated to "Manage List" page without signing in.

After

Page redirected to "Home" when clicking on "Manage List."

Testing Steps / QA Criteria

1. Without signing in, try navigate to "List" page using the navbar or direct URL (/list). Page should redirect to "Home."
2. Repeat for "Manage List."

[github-actions]

Visit the preview URL for this PR (updated for commit 1ad7245):

https://tcl-69-smart-shopping-list--pr52-jh-restrict-signout-cbhhbtp7.web.app

_{(expires Fri, 29 Mar 2024 22:36:56 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 93172cc46147b7d365c2b1b8239b61e2efb07a80}

[hsiangj]

The original idea was to implement useContext to share current user info. However, there is already a current user object from the useAuth hook set up in App.jsx.

[krsnamara]

Curious why you chose not to useContext?
I think the way you accomplished this was super clean and to the point.
Great work!

[piecanoe]

Looks great! Works as it should.

[amalyam]

Nice, works as expected!