Event form is located in a few places including Adding/Editing events in a Project. Example screenshot below:

Components to be converted should be Modal, Input, Select and Button

@JackHaeg @trillium Hi, question, the MUI linked is for "Base UI" which is now deprecated. A different PR used Material UI ( mui #1813 that fixes #1694), which package for MUI should I use?

Hey, please use the non-depricated package. If we need to install he correct MUI dependencies, please update package.json and yarn.lock in their own commit.

Hey thanks for the reply!

@trillium should we plan to use:

• Material MUI
  • used in the last pr that was merged
• Base UI
  • Most similar to the deprecated package of MUI Base which is the one linked in the ticket and other related issues
  • introduces an additional component package to the repo that may be redundant

Hey @sasszz, happy to clarify :)

Use Material MUI, the Base UI was a mistakely added resource

Hi @sasszz! When you have a moment, can you please provide an update with the following information:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

Hey Jack!

Draft PR open here: #1844

1. Progress - 50% - scoped out issue, understand component, about 1/2 through refactoring. Although it's one form, it has multiple components (Modal, Input, Select and Button), making it a larger ticket (more like 0.5)
2. Difficulties - I have 3:
   • Global CSS applied to all inputs make transition to MUI components tricky as the refactored MUI component has extra CSS acting upon it, resulting in weird dimensions/padding.
   • Should we consider extracting for example, the <Input> component to something reusable in other forms so we don't have to recreate it?
   • How close should I follow the styles of the prev component (pre-refactor)
3. Availability - 10 hours this week
4. If I could get advice on these blockers, I could get a final PR up EOW

@trillium just to confirm, adhering to current styles is not necessary? Maybe aim for close to the original component styles, but not exact?

Correct, for this component feel free to use your judgement on what needs to change

Update!

Progress: PR is completed and ready for review #1844 
Blockers: Awaiting other dev approvals
Availability: Ready for new task
ETA: This week, after review process is completed

Update!

Progress: PR has one approval and is awaiting 1 more
Blockers: Awaiting other dev approval
Availability: Ready for new task
ETA: Today after today's meeting