Controls

Storybook Controls gives you a graphical UI to interact with a component's arguments dynamically without needing to code. Use the Controls panel to edit the inputs to your stories and see the results in real-time. It's a great way to explore your components and test different states.

Controls do not require any modification to your components. Stories for controls are:

• Convenient. Auto-generate controls based on React/Vue/Angular/etc. components.
• Portable. Reuse your interactive stories in documentation, tests, and even in designs.
• Rich. Customize the controls and interactive data to suit your exact needs.

To use Controls, you need to write your stories using args. Storybook will automatically generate UI controls based on your args and what it can infer about your component. Still, you can configure the controls further using argTypes, see below.

Choosing the control type

Run the following command to install the tooling.

Update your angular.json file to include the following configuration to include it in the Storybook's inbuilt builder configuration.

Finally, update your .storybook/preview.ts file to include the following configuration to import the metadata generated by Compodoc and use it to generate the controls and argTypes for your stories.

When you set the component annotation of the meta (or default export) of your story file, it will be used to infer the controls and auto-generate the matching argTypes for your component.

Update your ember-cli-build.js configuration file to include the adapter.

Restart your application to generate the metadata file (i.e., storybook-docgen/index.json) and update your .storybook/preview.js file to include it, which will be used to create the controls and argTypes for your stories.

When you set the component annotation of the meta (or default export) of your story file, it will be used to infer the controls and auto-generate the matching argTypes for your component.

When you set the component annotation of the meta (or default export) of your story file, it will be used to infer the controls and auto-generate the matching argTypes for your component.

<IfRenderer renderer={[ 'html', 'svelte', 'preact', 'qwik', 'solid' ]}> By default, Storybook will choose a control for each arg based on its initial value. This will work well with specific arg types (e.g., boolean or string). To enable them, add the component annotation to the meta (or default export) of your story file, and it will be used to infer the controls and auto-generate the matching argTypes for your component provided by the framework you've chosen to use.

For instance, suppose you have a variant arg on your story that should be primary or secondary:

By default, Storybook will render a free text input for the variant arg:

It works as long as you type a valid string into the auto-generated text control. Still, it's not the best UI for our scenario, given that the component only accepts primary or secondary as variants. Let’s replace it with Storybook’s radio component.

We can specify which controls get used by declaring a custom argType for the variant property. ArgTypes encode basic metadata for args, such as name, description, and defaultValue for an arg. These get automatically filled in by Storybook Docs.

ArgTypes can also contain arbitrary annotations, which the user can override. Since variant is a component property, let's put that annotation on the defineMeta function, or the default export if you're using standard CSF.

ArgTypes can also contain arbitrary annotations, which the user can override. Since variant is a component property, let's put that annotation on the meta (or default export).

This replaces the input with a radio group for a more intuitive experience.

Custom control type matchers

Controls can automatically be inferred from arg's name with regex, but currently only for the color picker and date picker controls. If you've used the Storybook CLI to setup your project, it should have automatically created the following defaults in .storybook/preview.js|ts:

If you haven't used the CLI to set the configuration, or if you want to define your patterns, use the matchers property in the controls parameter:

Fully custom args

Until now, we only used auto-generated controls based on the component for which we're writing stories. If we are writing complex stories, we may want to add controls for args that aren’t part of the component. For example, here's how you could use a footer arg to populate a child component:

By default, Storybook will add controls for all args that:

• It infers from the component definition if your framework supports it.

• Appear in the list of args for your story.

Using argTypes, you can change the display and behavior of each control.

Dealing with complex values

When dealing with non-primitive values, you'll notice that you'll run into some limitations. The most obvious issue is that not every value can be represented as part of the args param in the URL, losing the ability to share and deep link to such a state. Beyond that, complex values such as JSX cannot be synchronized between the manager (e.g., the Controls panel) and the preview (your story).

One way to deal with this is to use primitive values (e.g., strings) as arg values and add a custom render function to convert them to their complex counterpart before rendering. It isn't the nicest way to do it (see below), but certainly the most flexible.

Unless you need the flexibility of a function, an easier way to map primitives to complex values before rendering is to define a mapping; additionally, you can specify control.labels to configure custom labels for your checkbox, radio, or select input.

Note that both mapping and control.labels don't have to be exhaustive. If the currently selected option is not listed, it's used verbatim.

Creating and editing stories from controls

This feature is not supported with the Svelte CSF. To opt-in to this feature with Svelte, you must use Storybook's [Component Story Format](../api/csf/index.mdx).

You can create or edit stories, directly from the Controls panel.

Create a new story

Open the Controls panel for a story and adjust the value of a control. Then save those changes as a new story.

Edit a story

You can also update a control's value, then save the changes to the story. The story file's code will be updated for you.

Disable creating and editing of stories

If you don't want to allow the creation or editing of stories from the Controls panel, you can disable this feature by setting the disableSaveFromUI parameter to true in the parameters.controls parameter in your .storybook/preview.js|ts file.

Configuration

Controls can be configured in two ways:

• Individual controls can be configured via control annotations.
• The panel's appearance can be configured via parameters.

Annotation

As shown above, you can configure individual controls with the “control" annotation in the argTypes field of either a component or story. Below is a condensed example and table featuring all available controls.

Parameters

Controls supports the following configuration parameters, either globally or on a per-story basis:

Show full documentation for each property

Since Controls is built on the same engine as Storybook Docs, it can also show property documentation alongside your controls using the expanded parameter (defaults to false). This means you embed a complete Controls doc block in the controls panel. The description and default value rendering can be customized like the doc block.

To enable expanded mode globally, add the following to .storybook/preview.js|ts:

Here's what the resulting UI looks like:

Specify initial preset color swatches

For color controls, you can specify an array of presetColors, either on the control in argTypes, or as a parameter under the controls namespace:

Color presets can be defined as an object with color and title or a simple CSS color string. These will then be available as swatches in the color picker. When you hover over the color swatch, you'll be able to see its title. It will default to the nearest CSS color name if none is specified.

Filtering controls

In specific cases, you may be required to display only a limited number of controls in the controls panel or all except a particular set.

To make this possible, you can use optional include and exclude configuration fields in the controls parameter, which you can define as an array of strings or a regular expression.

Consider the following story snippets:

Sorting controls

By default, controls are unsorted and use whatever order the args data is processed in (none). Additionally, you can sort them alphabetically by the arg's name (alpha) or with the required args first (requiredFirst).

Consider the following snippet to force required args first:

Disable controls for specific properties

Aside from the features already documented here, Controls can also be disabled for individual properties.

Suppose you want to turn off Controls for a property called foo in a component's story. The following example illustrates how:

Resulting in the following change in Storybook UI:

The previous example also removed the prop documentation from the table. In some cases, this is fine. However, sometimes you might want to render the prop documentation without a control. The following example illustrates how:

Conditional controls

In some cases, it's useful to be able to conditionally exclude a control based on the value of another control. Controls supports basic versions of these use cases with the if, which can take a simple query object to determine whether to include the control.

Consider a collection of "advanced" settings only visible when the user toggles an "advanced" toggle.

Or consider a constraint where if the user sets one control value, it doesn't make sense for the user to be able to set another value.

The query object must contain either an arg or global target:

It may also contain at most one of the following operators:

If no operator is provided, that is equivalent to { truthy: true }.

Troubleshooting

<IfRenderer renderer={['angular', 'ember', 'web-components']}>

Controls are not automatically generated for my component

If you're working with Angular, Ember, or Web Components, automatic argTypes and controls inference will not work out of the box and requires you to provide additional configuration to allow Storybook to retrieve the necessary metadata and generate the needed argTypes and controls for your stories. However, if you need additional customization, you can always define them manually. </IfRenderer>

The controls are not updating the story within the auto-generated documentation

If you turned off inline rendering for your stories via the inline configuration option, you would run into a situation where the associated controls are not updating the story within the documentation page. This is a known limitation of the current implementation and will be addressed in a future release.

API

Parameters

This feature contributes the following parameters to Storybook, under the controls namespace:

disable

Type: boolean

Disable this feature's behavior. If you wish to disable this feature for the entire Storybook, you should do so in your main configuration file.

This parameter is most useful to allow overriding at more specific levels. For example, if this parameter is set to true at the project level, it could then be re-enabled by setting it to false at the meta (component) or story level.

exclude

Type: string[] | RegExp

Specifies which properties to exclude from the Controls panel. Any properties whose names match the regex or are part of the array will be left out. See usage example, above.

expanded

Type: boolean

Show the full documentation for each property in the Controls panel, including the description and default value. See usage example, above.

include

Type: string[] | RegExp

Specifies which properties to include in the Controls panel. Any properties whose names don't match the regex or are not part of the array will be left out. See usage example, above.

presetColors

Type: (string | { color: string; title?: string })[]

Specify preset color swatches for the color picker control. The color value may be any valid CSS color. See usage example, above.

sort

Type: 'none' | 'alpha' | 'requiredFirst'

Default: 'none'

Specifies how the controls are sorted.

• none: Unsorted, displayed in the same order the arg types are processed in
• alpha: Sorted alphabetically, by the arg type's name
• requiredFirst: Same as alpha, with any required arg types displayed first

disableSaveFromUI

Type: boolean

Default: false

Disable the ability to create or edit stories from the Controls panel.