Storybook: MDX Props table doesn't display props of external library component

[dvh91]

I have a use-case where I want to document in my storybook a material-ui component and get all of it's props to be displayed in the table.

As a naive approach, here was my mdx doc file:

import { Meta, Story, Preview, Props } from "@storybook/addon-docs/blocks";
import { Button } from "@material-ui/core";

<Meta title="Button" component={Button} />

### Basic

<Preview>
  <Story name="Basic">
    <Button>
        Storybook
    </Button>
  </Story>
</Preview>

### Props

<Props of={Button} />

Unfortunately, I couldn't see any props in the table.

I'm consuming the compiled version material-ui component which includes a separated d.ts types file with all the relevant props and descriptions but I can't seem to load them properly.

[shilman]

We're updating the recommended configuration to use babel-plugin-react-docgen instead of react-docgen-typescript-loader, and they are tracking this issue here: https://github.com/reactjs/react-docgen/issues/416 please upvote!

[stale[bot]]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[amilaI]

Any update on a fix for this?

[shilman]

@amilaI no, and it's not on the roadmap. we've got our hands full correctly showing props for your own component library. showing props for external libraries is not a priority use case. should it be?

[dvh91]

@shilman IMHO, it should be. Material UI exposes theme customization that can generate most of the standard design system.
In addition to that, you add composition components and custom components.
At the same time, you want to encapsulate everything in one storybook.

[shilman]

point taken. to some extend we're at the mercy of the underlying docgen packages we're using (react-docgen / react-docgen-typescript) but i'll see what we can do

[nextglabs]

Having same issue, hope to get a fix soon