A decorator is a way to wrap a story in extra “rendering” functionality. Many addons define decorators to augment your stories with extra rendering or gather details about how your story is rendered.
When writing stories, decorators are typically used to wrap stories with extra markup or context mocking.
Some components require a “harness” to render in a useful way. For instance, if a component runs right up to its edges, you might want to space it inside Storybook. Use a decorator to add spacing for all stories of the component.
Some libraries require components higher up in the component hierarchy to render correctly. For example, in Styled Components, a
ThemeProvider is necessary if your components use themes. Add a single global decorator that adds this context to all stories in
In the example above, the theme is hardcoded to a mock value of
default. Still, you may want to vary that value, either on a per-story basis (if it is data you are mocking that is relevant to the other args of the story) or in a user-controlled way (for instance, to provide a theme switcher).
The second argument to a decorator function is the story context which in particular contains the keys:
args- the story arguments. You can use some
argsin your decorators and drop them in the story implementation itself.
argTypes- Storybook's argTypes allow you to customize and fine-tune your stories
globals- Storybook-wide globals. In particular you can use the toolbars feature to allow you to change these values using Storybook’s UI.
hooks- Storybook's API hooks (e.g., useArgs).
parameters- the story's static metadata, most commonly used to control Storybook's behavior of features and addons.
viewMode- Storybook's current active window (e.g., canvas, docs).
If your components are “connected” and require side-loaded data to render, you can use decorators to provide that data in a mocked way without having to refactor your components to take that data as an arg. There are several techniques to achieve this. Depending on exactly how you are loading that data -- read more in the building pages in Storybook section.
To define a decorator for a single story, use the
decorators key on a named export:
It is useful to ensure that the story remains a “pure” rendering of the component under test, and any extra HTML or components you need to add don’t pollute that. In particular the Source docblock works best when you do this.
To define a decorator for all stories of a component, use the
decorators key of the default CSF export:
We can also set a decorator for all stories via the
decorators export of your
.storybook/preview.js file (this is the file where you configure all stories):
Like parameters, decorators can be defined globally, at the component level, and for a single story (as we’ve seen).
All decorators, defined at all levels that apply to a story, will run whenever that story is rendered, in the order: