-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Info addon doesn't renders component description #4643
Comments
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! |
This certainly looks like a bug. @danielduan mind taking a quick look? @MihaChicken any chance you could put together a PR for this? |
@MihaChicken dang guys, you're 5 steps ahead. 😲 Will get that out soon. Thanks for making it happen! 🙇 |
…iption GH-4643 fix docgen description displaying for info addon
…iption GH-4643 fix docgen description displaying for info addon
This just went out in https://github.com/storybooks/storybook/releases/tag/v4.0.9, closing! Great work @MihaChicken 🎉 |
Bug or support request summary
I'm using Storybook with info-addon to auto create documentation based on Flow specification and jsdoc comments. The problem is that props table is displayed correctly but there is no component description. After debuging I found out that the problem is actually in this line:
https://github.com/storybooks/storybook/blob/master/addons/info/src/components/Story.js#L253
This condition in
if
statement is never truthful because left side is a component name but right side is a story description (like 'bold centered text with no margins').Changing the condition to:
if (STORYBOOK_REACT_CLASSES[key].name === context.kind) {
solves all the problems.Could anyone please tell me is it a bug or am I doing something wrong?
The text was updated successfully, but these errors were encountered: