Closed DiegoAndai closed 2 months ago
hmm I saw component being built in pigment-css, which I didn't expect. I thought those component will be part of base-ui, and that material-ui & joy-ui will use them or reexport them if needed.
I prefer making Grid v2 stable in v6 (without renaming the name) and deprecating the Grid v1.
I think it's the right time to get rid of the Grid v1 because the v2 is using gap
by default thanks to @DiegoAndai. It's much better and I think the community will like it.
For the docs, I think we can swap so /material-ui/react-grid
presents the new Grid and /material-ui/react-deprecated-grid
presents Grid v1.
I prefer making Grid v2 stable in v6 (without renaming the name) and deprecating the Grid v1.
For the docs, I think we can swap so /material-ui/react-grid presents the new Grid and /material-ui/react-deprecated-grid presents Grid v1.
I agree, this approach makes sense 👍🏼
Is #42000 about the same issue?
Is #42000 about the same issue?
Yes, I'm closing it.
What's the problem?
The Grid v2 component is marked as unstable. With the addition of the Pigment Grid, a stable no-runtime alternative with the same API, we should mark the Grid v2 as stable.
Also, with three separate grid components, I worry it might get confusing to know which one to choose for users
Solution
Stabilize Grid v2 and deprecate Grid, making Grid v2 the option for runtime Grid.
Search keywords: gridv2 unstable grid