feat: Root Layout and Protected Routes #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To ensure that only authenticated users can access the Home route, I had to implement conditional redirection logic based on the user's authentication state. A common approach to doing this in React applications is to create a protected route component. What did I do?
This component checks whether the user is authenticated. If not, it redirects to the login page. If so, it allows access to the desired route.
Explanation
Navigate
component. If the user is authenticated, it renders theOutlet
component, which allows it to render the child components of the protected route.ProtectedRoute
component. This way, we guarantee that the Home route will only be accessible if the user is authenticated.Final considerations
ProtectedRoute
component.With these changes, we can ensure that the Home page will only be accessible to authenticated users and that unauthenticated users will be redirected to the login page.