It's useful to write stories that render two or more components at once if those components are designed to work together. For example, ButtonGroup, List, and Page components.
Subcomponents
When the components you're documenting have a parent-child relationship, you can use the subcomponents property to document them together. This is especially useful when the child component is not meant to be used on its own, but only as part of the parent component.
Here's an example with List and ListItem components:
Note that by adding a subcomponents property to the default export, we get an extra panel on the ArgTypes and Controls tables, listing the props of ListItem:
Subcomponents are only intended for documentation purposes and have some limitations:
- The argTypes of subcomponents are inferred (for the renderers that support that feature) and cannot be manually defined or overridden.
- The table for each documented subcomponent does not include controls to change the value of the props, because controls always apply to the main component's args.
Let's talk about some techniques you can use to mitigate the above, which are especially useful in more complicated situations.
Reusing story definitions
We can also reduce repetition in our stories by reusing story definitions. Here, we can reuse the ListItem stories' args in the story for List:
By rendering the Unchecked story with its args, we are able to reuse the input data from the ListItem stories in the List.
Creating a Template Component
Another option that is more “data”-based is to create a special “story-generating” template component:
This approach is a little more complex to setup, but it means you can more easily reuse the args to each story in a composite component. It also means that you can alter the args to the component with the Controls addon.