Open DiegoAndai opened 8 months ago
Hi @DiegoAndai,
I would like to help out with this task, I'm thinking of starting with tooltip, but I'm having a little difficulty discerning the composed classes from the atomic ones. I'm looking at the docs docs, would I be correct in assuming that the merge request should look something along the lines of:
.MuiTooltip-arrow .MuiTooltip-popper .MuiTooltip-popperArrow [deprecated] .MuiTooltip-popperClose [deprecated] .MuiTooltip-popperInteractive [deprecated] .MuiTooltip-tooltip .MuiTooltip-tooltipArrow .MuiTooltip-tooltipPlacementBottom [deprecated] .MuiTooltip-tooltipPlacementLeft [deprecated] .MuiTooltip-tooltipPlacementRight [deprecated] .MuiTooltip-tooltipPlacementTop [deprecated] .MuiTooltip-touch
Where the composed classes are the the joins of what would be individual css classes applied to the children.
Hi @harry-whorlow! The Tooltip components is a complex component, I'm not sure what the best class structure would be best 🤔
I would suggest starting with the SpeedDial component.
Copy that, I'll start with the old friend SpeedDial 🫡
[edit]: I've had a lot of things come up, if someone wants to take over go ahead. I'll update this comment if something changes in the future. Sorry
Hi @DiegoAndai
I would like to help out with this task. Is it still available for contribution from the community?
Hello @DiegoAndai, I would like to contribute as well. Which of the remaining components would you recommend?
Part of #40417
Description
Deprecate composed CSS classes, which are planned for removal in v7.
Example PR
Contributing
Feel free to take any components that still need to be done or in progress. Please mention this issue in your PR so we can link it in the description and keep it up to date.
Components to migrate
Search keywords: deprecation composed classes material-ui
Search keywords: