Replies: 2 comments 3 replies
-
I agree this is a good feature. There's an undocumented way of doing this today--we didn't document it because there was no consensus on what the API should be. I'll sketch that out here for discussion's sake. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Passing this as accepted as we discussed we'd switch it to an open issue in a refinement a few weeks back. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Provide a mechanism to:
Problem Statement
As the number of Storybook addons, so does the number of addon panels.
In many case, not all panels are useful for a specific story.
It cluttered the UI, making it harder to use.
There also could be performance impact.
But currently, there seems to be no way to control which panel to hide per story.
Non-goals
.storybook/manager.ts
Implementation
For the addon author, the
useChannel({ STORY_CHANGED: ... })
may already have sufficient information, but I have not work on creating aPanel
yet so I'm not 100% sure.The bottom line is allow the author to do this:
For the consumer,
allow them to control which panel to hide.
One way is adding a specific prop:
Another way is use the same syntax as in
tags
, which allow the panels to be sorted too:Prior Art
No response
Deliverables
No response
Risks
No response
Unresolved Questions
Alternatives considered / Abandoned Ideas
No response
Beta Was this translation helpful? Give feedback.
All reactions