PropTypes for documentation authors.
Typable is a React PropTypes wrapper that allows for easy extraction of your type metadata.
npm i prop-types typable-react
Type your components like this instead of using propTypes. This will implicitly apply propTypes
import typed from 'typable-react'
export default function MyComponent({
name,
fruitCount,
fruit
}) {
return <h1>Hello {name}, I ate {fruitCount} {fruit}</h1>
}
typed(MyComponent, {
name: {
type: typed.string,
required: true,
description: 'The name to be greeted'
},
fruitCount: {
type: typed.number,
default: 0,
description: 'The number of fruit eaten'
},
fruit: {
type: typed.oneOf(['bananas', 'mangoes']),
default: 'bananas',
description: 'The number of fruit eaten'
},
})
When you need to extract the type metadata for documentation, it's all available at MyComponent.types
.
console.log(MyComponent.types)
/*
{
name: {
type: 'string',
required: true,
description: 'The name to be greeted'
},
fruitCount: {
type: 'number',
default: 0,
description: 'The number of fruit eaten'
},
fruit: {
type: { name: 'oneOf', params: ['bananas', 'mangoes'] },
default: 'bananas',
description: 'The number of fruit eaten'
},
}
*/
and your installed version of prop-types is applied
MyComponent.propTypes = {
name: PropTypes.string.isRequired,
fruitCount: PropTypes.number,
fruit: PropTypes.oneOf(['bananas', 'mangoes'])
}
MyComponent.defaultProps = {
fruitCount: 0,
fruit: 'bananas'
}
PropTypes is great for regular use but when building components that need to be documented, it does not give any information about the prop types that can be easily extracted into the documentation. Documentation tools currently use react-docgen or similar implementation to extract by reading the entire source file to parse PropTypes syntax. This is not always straightforward to use as it may require raw loading components to be parsed as strings.
typable-react is MIT licensed. Read details