You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our storybook utils to disable/hide/move component props in the controls table are currently generating and returning objects without context of any existing entries on the config it adds to (component or story level). While Storybook does merge configs (component and story level - story level overwrites component level) this can still result in the utils output potentially overwriting existing prop control definitions - e.g. when we call multiple utils on the same prop and in the same level (e.g. story level).
We want to update the utils to ensure they update the existing config instead of overwriting it.
utils (hideStorybookControls, disableStorybookControls and moveStorybookControlsToCategory) don't overwrite other config entries but mutate the existing config while respecting existing entries
props that are adjusted in the controls panel via utils are properly output (e.g. moved and disabled)
The text was updated successfully, but these errors were encountered:
Summary
Our storybook utils to disable/hide/move component props in the controls table are currently generating and returning objects without context of any existing entries on the config it adds to (component or story level). While Storybook does merge configs (component and story level - story level overwrites component level) this can still result in the utils output potentially overwriting existing prop control definitions - e.g. when we call multiple utils on the same prop and in the same level (e.g. story level).
We want to update the utils to ensure they update the existing config instead of overwriting it.
💬 See this conversation for more information.
Acceptance criterea
hideStorybookControls
,disableStorybookControls
andmoveStorybookControlsToCategory
) don't overwrite other config entries but mutate the existing config while respecting existing entriesThe text was updated successfully, but these errors were encountered: