-
Notifications
You must be signed in to change notification settings - Fork 842
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
EuiIcon is missing props #3185
Comments
Can I give it a try? |
@myasonik react-docgen plugin is not generating __docgenInfo property of EuiIcon, After debugging custom plugin proptypes-from-ts-props and react-docgen, I found this error (in react-docgen) is stopping __docgenInfo generation. I wonder if anything is missed out in proptypes-from-ts-props plugin or It is issue of react-docgen itself. |
@Marvin9 Are you trying it still or should I try to fix? |
You can try @walter-ind |
Thanks @Marvin9 |
Figured out, if we manually remove if statement which is throwing error, we got result. In short, the problem is with dynamic import which is not recognized by ast-types. This issue will be solved in #3056 |
There is one more way by which this issue can be fixed |
EUI team, what do y'all think? I've got no idea. |
This is fine as a short term solution. If you make this, I'd advise against listing the entire icon list (since it is fairly long) for the |
I know it would be too long. It's better to make one solution that stays for long. So better, let it be fixed by #3056. |
The icon props display for me, locally. Is this something that has already been fixed on master, or is it a problem with the docs' production build? |
@chandlerprall I think it's a problem is in the doc's production build. I can see the icons props locally but in a build, it doesn't show up: https://eui.elastic.co/pr_3200/#/display/icons |
I just did a docs build locally ( |
Latest release cleared up this issue. Will monitor the builds the next few docs syncs to see if there is something flakey here. |
EuiIcon seems to be missing props
The text was updated successfully, but these errors were encountered: