-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logic as standalone npm module #42
Comments
What you you mean by the logic? The UI is core part of Storybook. |
We already have an application that provides a visual overview for all our patterns. I do not want to setup another tool that provides the same thing with just another featureset. here would be an imaginary flow on how to use the logic of this project in my application:
// my-stories.js
// ...
import { storiesOf } from '@kadira/storybook';
storiesOf('Button', module)
// register stories... // navigation.js
// ...
import { storiesOf } from '@kadira/storybook';
storiesOf('Button').forEach(story => /* my implementation of rendering a nav-entry */); // view.jsx
// ...
import { StoryView } from '@kadira/storybook';
<MyPatternlab>
<MyNavigation></MyNavigation>
<StoryView for=currentStory></StoryView>
</MyPatternlab> This way I could use this as a less opinionated subcomponent in my own solution. |
Okay got it. Good idea. |
Remove <div> wrapper from WrapStory
probably it should be --save-dev in README example?
Update babel-eslint to version 5.0.0 🚀
Storybook stories are extractable see for example how storyshots is doing it: |
I really love the idea of building a DSL for state mutations. Since this comes as a standalone application it's not possible to integrate it in existing pattern lab solutions. (And I would really like to do that, instead of reinventing the wheel here ;)
So any plans to distribute the logic as a standalone npm module without the UI?
The text was updated successfully, but these errors were encountered: