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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
In Storybook v8 the subcomponent API will come back.
While it works great there a few things that would make it better, like provide additional options for documentation.
For example currently we are documenting the subcomponents at @neo4j with custom
pagecomponents under:This allows us to write descriptions about subcomponents and their usage.
Describe the solution you'd like
To have a modified
subcomponentsinterface, where it would allows something along the lines:Where custom description ideally it would be a component we could render (
ReactNode)Describe alternatives you've considered
Currently the alternative, was what we developed to mitigate the lack of
subcomponentsAPI, which is to create custompagerender functions.Are you able to assist to bring the feature to reality?
yes, I can
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions