Epic: Review file tree and update MUI Components

[JackHaeg]

Overview

Currently, components throughout the VRMS app do not match - some use MUI styling while others do not, thus creating a fractured user experience. All components throughout the VRMS file tree below must be updated to Material-UI components.

What if we're unable to access the component listed

Do your best to change the HTML elements out anyway and note in the PR that you're unable to get the component to render within VRMS for screenshots.

Should I try to match the CSS of the app beforehand

No, there will be some changes to the look and feel of the app switching to MUI components, we plan on going back in a second set of issues to match the CSS to our current figma design or a new figma design as it comes available.

Action Items

Check off these items when we have fully moved from standard HTML components to MUI components (note that same may already be updated to MUI). Each can be broken into its own issue.

• [x] #1623
• [x] #1625
• [ ] #1626
• [x] #1640
• [x] #1641
• [x] #1642
• [x] #1648
• [x] #1649
• [x] #1657
• [ ] #1671
• [x] #1672 [ closed, unused component ]
• [x] #1679 [ closed, unused component ]
• [ ] #1680
• [x] #1681 [ closed, unused component ]
• [x] #1682 [ closed, unused component ]
• [ ] #1683
• [ ] #1684
• [ ] #1693
• [ ] #1694
• [ ] #1698
• [ ] #1699
• [ ] #1700
• [ ] #1701
• [ ] #1665
• [ ] #1703
• [ ] #1704
• [ ] #1705
• [ ] #1707
• [ ] #1708
• [x] #1709 [ closed, unused component ]
• [ ] #1710
• [ ] #1711
• [ ] #1712
• [ ] #1713
• [ ] #1714
• [ ] #1715
• [ ] #1716
• [ ] #1717
• [x] #1718
• [ ] #1719
• [ ] #1720
• [ ] #1721
• [ ] #1722

Resources/Instructions

https://mui.com/base-ui/all-components/

[trillium]

#1549 has a list of all the files with jsx

./src/components/ProjectForm.js
./src/components/Navbar.js
./src/components/auth/Auth.js
./src/components/auth/HandleAuth.js
./src/components/user-admin/EditUsers.js
./src/components/user-admin/AddNewProject.js
./src/components/user-admin/UserManagement.js
./src/components/admin/donutChartContainer.js
./src/components/admin/donutChartLoading.js
./src/components/admin/dashboard/index.js
./src/components/admin/donutChart.js
./src/components/admin/reports/index.js
./src/components/dashboard/AddTeamMember.js
./src/components/dashboard/RosterTable.js
./src/components/dashboard/RosterTableRow.js
./src/components/presentational/CheckInButtons.js
./src/components/presentational/returnUserForm.js
./src/components/presentational/newUserForm.js
./src/components/presentational/profile/UserTable.js
./src/components/presentational/upcomingEvent.js
./src/components/manageProjects/eventForm.js
./src/components/manageProjects/editableField.js
./src/components/manageProjects/editMeetingTimes.js
./src/components/manageProjects/editProject.js
./src/components/manageProjects/addProject.js
./src/components/parts/form/ValidatedTextField.js
./src/components/parts/boxes/TitledBox.js
./src/components/Form.js
./src/components/Leaderboard.test.js
./src/components/Footer.js
./src/pages/Events.js
./src/pages/CheckInForm.js
./src/pages/ProjectLeaderDashboard.js
./src/pages/UserAdmin.js
./src/pages/UserProfile.js
./src/pages/ReturningUser.js
./src/pages/Home.js
./src/pages/ProjectList.js
./src/pages/ManageProjects.js
./src/pages/NewUser.js
./src/pages/SecretPassword.js
./src/App.js

[trillium]

Hey all, @chukalicious was asking what we should do for components that aren't being used and aren't accessible if they're in this MUI update list.

We should close those issues as unplanned and mark in the list after the issue number that the component isn't used in the current iteration of the app.

eg

• [x] #1681 [ closed, unused component ]

And inside that issue mark it as unplanned

[JackHaeg]

@trillium Can you please close issues containing components that are not being used, add text: [ closed, unused component ] next to these issues, and make an update to this issue within the section "What if we're unable to access the component listed."

[trillium]

@JackHaeg Done :)