Implement login redirection and user info population #12
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.
Related to #11
Implements the login functionality and user information persistence across the site, as well as styling the login page to match the site's design.
src/Routes/Login.js
to include a login form that captures the user's name, stores it in local storage, and clears it at the end of the day. It also redirects the user to the home page upon successful login.src/App.js
to add a route for the Login component and implements a check for user information in local storage on app load. Redirects to the Login component if no user information is found.src/components/CallerCallHistory.js
andsrc/components/CallerTreatmentHistory.js
to populate "with" fields in call and treatment logs with the user's name from local storage if available.src/styles/routes/Login.css
to style the Login component, ensuring it aligns with the site's overall design.For more details, open the Copilot Workspace session.