-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
What to do with storybook? #3268
Comments
|
As of today, there are plenty of alternatives for storybook:
I would favor a solution that allows us to do reliable visual regression tests. The best (FOSS-)tool I know to achieve the latter is BackstopJS (https://github.com/garris/BackstopJS). It is not coupled to any particular styleguide, so anything lightweight (and preferably low on dependencies) will be good. However, as a first step I would argue in favor of A, because our storybook integration has actually no benefit atm. As a side note: |
The only current upside i see in story book is to have a guideline how to composit more complex components (like a dragable tree item) - but then again even these stories are mostly outdated and always reachable via gits history |
With my latest cleanups i completely removed any left over storybook dependencies and configs. |
Can this be closed, @mhsdesign? |
As long as we still have the .story.js lying around lets keep it open |
A: Totally abandon and remove it
B: start reusing it again (partly) is totally broken for now because of #3200
C: using alternatives #3268 (comment)
The text was updated successfully, but these errors were encountered: