You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Emotion to create new components, for example:
exportconstBaseButton=styled.button` border: none; padding: 0; width: auto; overflow: visible; background: transparent; /* inherit font & color from ancestor */ color: inherit; font: inherit; /* Normalize line-height. Cannot be changed from normal in Firefox 4+. */ line-height: normal; /* Corrects font smoothing for webkit */ -webkit-font-smoothing: inherit; -moz-osx-font-smoothing: inherit; /* Corrects inability to style clickable input types in iOS */ -webkit-appearance: none; /* Please provide appropriate focus styles */ :focus { outline: none; } /* Remove excess padding and border in Firefox 4+ */ &::-moz-focus-inner { border: 0; padding: 0; } cursor: ${({ disabled })=>(disabled ? "not-allowed" : "pointer")};`;
But this component can't be detected by Zeplin command (react-docgen).
I use TypeScript, so it is possible to figure out this is React component based on type infor
As an intermediate solution I would agree to have an option to detect name of component based on filename and skip properties parsing, because typically people have one component per file and same name for file and component.
The text was updated successfully, but these errors were encountered:
I use Emotion to create new components, for example:
But this component can't be detected by Zeplin command (react-docgen).
I use TypeScript, so it is possible to figure out this is React component based on type infor
As an intermediate solution I would agree to have an option to detect name of component based on filename and skip properties parsing, because typically people have one component per file and same name for file and component.
The text was updated successfully, but these errors were encountered: