Upgrade MUI to v6 and handle breaking changes

MIT-CAVE / cave_static

A react based static web app to be used as a UI and data consumer for the CAVE app.

Apache License 2.0

0 stars 1 forks source link

Upgrade MUI to v6 and handle breaking changes #559

Open luisvasq opened 2 months ago

luisvasq commented 2 months ago

We'd need to handle breaking changes, migration steps, and deprecated APIs:

[ ] Identify and fix any breaking changes introduced in MUI v6
[ ] Handle deprecated props / components / features and replace them with the updated alternatives
[ ] Test the functionality to ensure it remains the same after the upgrade

Refs:

luisvasq commented 2 months ago

Using the official codemod(s) is fine, but let's make sure to run npm run lint afterwards.

luisvasq commented 1 month ago

To support some updates in #499, I've upgraded MUI to v6. So far, I haven't found any issues, but the tasks in the checklist should remain the same.

luisvasq commented 1 month ago

Nice job with ClassicLegend, @ellawang9! There's only one migration issue: getting the dropdowns to fill up the available space. I think this is related to finding Grid2's equivalent of the Grid's xs prop when set to true.

legend-issue

ellawang9 commented 1 month ago

Thanks for pointing this out, Luis! Should be fixed now.