Replies: 2 comments 1 reply
-
Hi About the JS typo and inconsistencies, this is clearly a pain and it occurred several times in the past. It would clearly better to have examples written in TypeScript to catch such issues easily. I have done some archeology to try to understand why we choose Storybook, but I didn't find a clear answer |
Beta Was this translation helpful? Give feedback.
-
I have started working on bumping examples to storybook v7 in #230. |
Beta Was this translation helpful? Give feedback.
-
💡 Is there any plans on porting examples to Typescript? Because now it's just a little strange to fix some typos and inconsistencies in js stories (like #125
perimeter
) when library itself written in Typescript.I tried to write story in Storybook on Typescript with no success - there are sophisticated ways of configuring stories build and I eventually gave up 😿 . In addition, I don't see any benefits from Storybook in current state, besides search box and organizing stories, which can be made easily without it.
And if we have plans on dedicated page (maybe on github.io) it will be benefitial to have own example page, so users not forced to run Storybook. Or, alternatively, there is still posibility to setup Storybook and push it to github.io or some page.
Beta Was this translation helpful? Give feedback.
All reactions