Skip to content
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

[core] Remove React.ReactElement<any> from describeConformance.tsx #44318

Merged
merged 6 commits into from
Nov 26, 2024

Conversation

sai6855
Copy link
Contributor

@sai6855 sai6855 commented Nov 4, 2024

part of #42380

With this PR all of React.ReactElement<any> types are removed, except in base and joy files

@sai6855 sai6855 marked this pull request as draft November 4, 2024 07:13
@sai6855 sai6855 added typescript core Infrastructure work going on behind the scenes labels Nov 4, 2024
@sai6855 sai6855 changed the title [test-utils] Remove React.ReactElement<any> from describeConformance.tsx [core] Remove React.ReactElement<any> from describeConformance.tsx Nov 4, 2024
@mui-bot
Copy link

mui-bot commented Nov 4, 2024

Netlify deploy preview

https://deploy-preview-44318--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against f28b61e

@sai6855 sai6855 requested a review from DiegoAndai November 4, 2024 07:39
@sai6855 sai6855 marked this pull request as ready for review November 4, 2024 07:40
Copy link
Member

@DiegoAndai DiegoAndai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one comment 😊

} & React.RefAttributes<HTMLDivElement>
>;
};
components: {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should make components and componentsProps optional (?), as they're deprecated APIs and their usage is optional (with the testLegacyComponentsProp flag).

Is there a way for us to do that and silence the warnings that might appear inside the testLegacyComponentsProp tests?

@DiegoAndai DiegoAndai merged commit fdd856d into mui:master Nov 26, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes typescript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants