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
Addons extend and improve the Storybook workflow. Storybook has keyboard shortcuts that allow you to quickly manipulate the UI (the manager in Storybook parlance). But there's no easy way for addons to add their own custom the keyboard shortcuts. Instead, addon authors have to manually detect key downs to invoke their addons.
Describe the solution you'd like
Storybook addons should be able to define their own hotkeys like in VSCode.
Describe alternatives you've considered
The alternative is the status quo: addon authors manually implementing keyboard shortcuts.
Are you able to assist to bring the feature to reality?
No
Additional context
I designed the keyboard shortcuts UX in Storybook 5.0. It was modeled after VSCode. The UI doesn't need to change much to support this feature.
The text was updated successfully, but these errors were encountered:
We’re cleaning house! Storybook has changed a lot since this issue was created and we don’t know if it’s still valid. Please open a new issue referencing this one if this is still relevant in SB 7.x.
Addons extend and improve the Storybook workflow. Storybook has keyboard shortcuts that allow you to quickly manipulate the UI (the
manager
in Storybook parlance). But there's no easy way for addons to add their own custom the keyboard shortcuts. Instead, addon authors have to manually detect key downs to invoke their addons.Describe the solution you'd like
Storybook addons should be able to define their own hotkeys like in VSCode.
Describe alternatives you've considered
The alternative is the status quo: addon authors manually implementing keyboard shortcuts.
Are you able to assist to bring the feature to reality?
No
Additional context
I designed the keyboard shortcuts UX in Storybook 5.0. It was modeled after VSCode. The UI doesn't need to change much to support this feature.
The text was updated successfully, but these errors were encountered: