Storybook: DocPage: Prop table does not appear in the Docs panel if a component is exported wrapped in a React.memo function

Created on 9 Oct 2019  路  9Comments  路  Source: storybookjs/storybook

Describe the bug
Proptypes tabel does not appear in the Docs panel if a component is exported wrapped in a memo function.

For example
export default React.memo(Button)

To Reproduce
Steps to reproduce the behavior:

  1. Create regular React component
  2. Export component wrapped in React.memo function
  3. Run storybook
  4. Open Doc panel
  5. The prop table does not appear.

Expected behavior
The prop table does appears when component exported wrapped in React.mem()

docs props bug has workaround inactive

Most helpful comment

Unsatisfying workaround is to also export your pure component and use that for documentation purposes 馃槶

All 9 comments

Related: #7933

In my case (component wrapped with React.memo) props documentation is not displayed automatically. I used this workaround https://github.com/storybookjs/storybook/issues/8435#issuecomment-547075209 (exporting wrapped component) and now props are displayed fine.

@shilman

This should be fixed by https://github.com/storybookjs/storybook/pull/8665

Similar problem with forwardRef. The code and the "docs" tab:

Without forwardRef:

Screenshot at Nov 08 17-08-21
Screenshot at Nov 08 17-11-13

With forwardRef:

Screenshot at Nov 08 17-13-15
Screenshot at Nov 08 17-14-40

Version:

Screenshot at Nov 08 17-09-21

presets.js

Screenshot at Nov 08 17-34-00

Unsatisfying workaround is to also export your pure component and use that for documentation purposes 馃槶

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!

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!

This issue seems to be still unfixed but the stale bot closed it. Any updates?

Dupe to #9586

Was this page helpful?
0 / 5 - 0 ratings