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
@kazupon am I right to say if we follow those patterns, we would want to get passed a Vue Component instance rather than a set of options (which is basically the input to new Component()), which is what is currently passed around?
I do wonder whether the storybook API should be something like:
.add('name',newComponent(options));
Rather than:
.add('name',()=>options);
I'm not really sure and far from a Vue expert, so of course I totally defer to your opinion here, just wanted to point something out about decorators that I noticed when working on knobs stuff.
It's possible to write simple "DOM wrapping" decorators in the new Vue API, but a bit clunky:
It would be cool if somehow we registered the story as
story
as per the Vue component API and allowed you to write instead:I'm not quite sure how to do that ;) but it seems conceptually possible anyway. Would love to hear thoughts.
The text was updated successfully, but these errors were encountered: