jquense / docpocalypse Goto Github PK

Hey jquense,

I am working on a similar project which contains automated documentation, also.

I found your work on react-docgen-styled-resolver which would be very useful for me as well.

I use styled (emotion) components a lot, sometimes even extending them like:

import styled from '@emotion/styled'

const Base = styled.div``

Base.propTypes = {
// Proptypes for basic features
...
}

export default Base

and then having multiple components extending that base component:

import styled from '@emotion/styled'
import Base from './base'

const Extended = styled(Base)``

Extended.propTypes = {
...Base.propTypes,
// Proptypes for features specific to this component
...
}

export default Base

These adding single-purpose features with shared base features & styling.

For Example a with special features as base and a CTA extending that one. Giving the end-user the same features as a link but with different styling and maybe a new prop for a "open in new tab" feature.

So my questions:

• Whats the overall status of your styled components resolver?
• You think supporting that pattern of extending another component would be possible to support? (basically detect ...Base.propTypes,)
• I can help working on the resolver, we just need to figure out where and what :)

Best,
Benedikt