sai chand

Yup, I'll fix it. Thanks

@DiegoAndai Sounds good !! I'll wait for codemods and migration guide and update PRs accordingly

hey @DiegoAndai i've found a bug in accordion-props codemod PR and created a PR for it https://github.com/mui/material-ui/pull/40855, can you check that as well. off-topic: can you add https://github.com/mui/material-ui/pull/40687 to this...

> @sai6855, what are we missing for the Pagination components? Are we done after #41145? sorry missed this, `PaginationItem` does have `components` prop that needs to be deprecated. it also...

Below tests are not removed , because `describeConformance` test suite is not customizable enough to handle `PaginationItem`. https://github.com/mui/material-ui/blob/73c88b6c3f71287a4a1f0b1b5d7d37ab268dca49/packages/mui-material/src/PaginationItem/PaginationItem.test.js#L29-L31 I see 2 inconsistencies in `PaginationItem` compare to other components. 1. `properties`...

> fix this issue so we can stop skipping the slots tests? No, it didn't helped. even on removing `testLegacyComponentsProp: true` tests are failing.

> otherwise, we can cover the slots testing in PaginationItem tests. @DiegoAndai shall i go ahead with this approach?

@DiegoAndai added tests to test conditional slots

I think most of the above classes selector behavior can be achieved by combining the FilledInput root class and the `has` selector. Even if we add them now, they can...

>By removing classes, consumers would need to know about components' implementation details that classes help abstract. @aarongarciah I'm not sure if you are aware of this issue https://github.com/mui/material-ui/issues/41282 but TL...