Type error when setting component on DialogContentText

[Slessi]

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

This:

<DialogContentText component="div" />

Throws:

Property 'component' does not exist on type 'IntrinsicAttributes & DialogContentTextProps & { children?: ReactNode; }'. TS2769

Expected Behavior 🤔

Should accept component as a valid prop

Steps to Reproduce 🕹

https://codesandbox.io/s/charming-mccarthy-mx1kf

Steps:

1. Load sandbox URL
2. Wait a while... takes long for the error to appear

Context 🔦

I want the component to be a div so I can put <ul> inside which would be invalid inside a <p>

Your Environment 🌎

Tech	Version
Material-UI	4.8.2
React	16.12.0
Browser	Chrome
TypeScript	3.7.4

{
    "compilerOptions": {
        "baseUrl": "src",
        "target": "es5",
        "lib": ["dom", "dom.iterable", "esnext"],
        "allowJs": true,
        "skipLibCheck": true,
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "strict": true,
        "forceConsistentCasingInFileNames": true,
        "module": "esnext",
        "moduleResolution": "node",
        "resolveJsonModule": true,
        "isolatedModules": true,
        "noEmit": true,
        "jsx": "preserve",
        "downlevelIteration": true,
        "importHelpers": true
    },
    "include": ["src"]
}

[shorn]

Problem seems to have been introduced with 4.8.1 and affects other components like Drawer, see https://stackoverflow.com/q/59494907/924597

[fyodor-e]

DialogContentText component is wrapper around Typography. As Typography type definition has been changed, DialogContentText also should be updated. I'll do it.

But I don't see any realtion to Drawer component. It is not depend on Typography and not use component prop. @shorn , could you please describe what is wrong with Drawer

[shorn]

@fyodore82
Regarding Drawer - I'm not sure. It was actually someone else who commented on the SO linked question saying they had the same problem but with Drawer.

[JamieS1211]

The draw issue was was caused because the "component" prop is not available on Drawer and unused props on Drawer are not forwarded onto a component that supports the "component" prop. Confusion was caused by some wording of the docs that was cleaned up here - #19015

[fyodor-e]

I've looked at Drawer component, It does not expect component prop. Drawer uses either div or Modal internally. Modal also does not support component prop

Do you means that we should add comoponent prop to Drawer?

[shorn]

Sounds like Drawer never took component in the first place, but it was implied by the doco that it did.
If someone wants to refactor Drawer so that it does allow specification of a component - it seems like that should be a separate issue.