-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Grid2] Rollout plan #43437
Comments
The plan looks good overall, @oliviertassinari 👌🏼 The only step I'm not sure of is:
I don't know the long-term vision for the system package, and we need to solve that before setting the goal of moving everyone to import Grid from it. This is not the issue to discuss this. @aarongarciah and @colmtuite should probably lead the discussion. |
@DiegoAndai Alright, I have removed that step. Since this new Grid has been here for about 6 months but we haven't completed the work, and since we can't start anything new until we finish what we started (so we only start things we have the bandwidth to see through), I have tried to help a bit with step 3. in https://github.com/mui/mui-private/pull/685. I have struggled a bit, it was frustrating, I think that we have clear opportunities to turn this into a great DX. I believe we need to do:
![]() I think we need a custom prop type instead, that clearly explain that this is a Grid v1 prop, that you can now remove the prop.
![]()
|
@DiegoAndai What's the checkboxes PR will cross? I can help with the one that the PR hasn't addressed. |
Hey @siriwatknp, #45304 will complete 0.a, 0.b, and 0.c. I've already started working on the other steps but need #45304 to be merged first. I'll let you know if I need help with any of these 👍🏼 |
I'll move this issue out of the v7 milestone and into the v8 one. All work for v7 has been completed, the only thing missing from the tasks is to remove |
Summary
We recently made Grid v2 stable, #43054 so now it's time to look at the rollout plan, effectively to get completely get rid of the old one.
A possible action plan:
<Grid2 item>
. It says:I think we need a custom prop type instead, that clearly explain that this is a Grid v1 prop, that you can now remove the prop.
<Grid2 xs={12}>
. The attribute gets silently applied to the DOM:0.c. I got the impression that the migration guide was started but not finished: https://mui.com/material-ui/migration/migration-grid-v2/. I couldn't rely a lot on it. The problems I saw:
xs
,sm
, etc. props.1. Update the h1 in https://next.mui.com/material-ui/react-grid/ to mention deprecated, so Google and Algolia search results are clear
2.
Reexport Grid v2 from@mui/system/Grid2
getting one step closer to move everyone imports from @mui/material to mui/system [RFC] Remove @mui/material default theme and @mui/system, @pigment-css/react reexports #405943. Migrate all the MUI codebase to the Grid v2
4. Introduce a deprecation warning when using Grid v1 [material-ui] Deprecate system props #42259
5. In the next major swap the implementation for the Grid namespace, put the deprecated Grid v1 into the exported GridLegacy namespace
6. In the major after that next major, remove GridLegacy.
Motivation
Simplicity
The text was updated successfully, but these errors were encountered: