-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Component being omitted from output for no reason #549
Comments
Does it work if you roll back to v5? And the "jsx static" bit in the middle of your .md file looks weird -- is this is a formatting error or...? |
Please make a demo project that we can debug based on this repo: https://github.com/styleguidist/example |
So i went ahead and made a demo and nailed it down to the line that is causing the issue. My PropTypes are:
NotificationPropTypes is:
This is causing an issue as follows when I compile in the example project: If I change the PropTypes to be there inline in the file, it works:
Problem is, I prefer to have them separate files as I like to export them for use in the containing project as well. Is there no way around this? How should I export the props (preferably in a separate file) so that they get read properly? |
I should also point out that this is related to my question here: #548 |
This looks like a react-docgen issue and should be reported in their repo. |
Looks like this is already a long standing issue there: reactjs/react-docgen#33 Closing this and following there, thanks. |
I'm using 6.0.0 beta.2 and I have a single component out of all of my UI kit that is not being shown for no apparent reason. I don't have any settings in my config that would ignore this component. Every single other component in my project that's in the same directory structure as this one is outputting correctly in my SG.
NotificationContainer.jsx
NotificationContainer.md
I can't for the life of me figure out what it is about this component that is different from all others and making it not get parsed.
The text was updated successfully, but these errors were encountered: