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
I think people will expect something along the lines of,
It’s best practice to use [a typescript interface] in React to specify the shape of data that a component expects.
Additional context
I'm new to storybook, but I have the impression it is the industry standard. Typescript is also industry standard, so I hope to see these technologies play nicely together.
I'm actually struggling to setup storybook in a monorepo (very common in industry today) with typescript and multiple React applications sharing one component library. I want storybook to run in the package for the component library.
The text was updated successfully, but these errors were encountered:
@cyrfer, thanks for following up with us on this and indeed, you're right 🙇 . The tutorials are not up-to-date with TypeScript. Hope you don't mind, but I'm going to close this one, and let's continue the discussion on the tutorial's repository issue here
Describe the issue
For newcomers to storybook, it is confusing to see
I think the community moved to typescript interfaces for this some time ago.
Steps to reproduce the behavior
Expected behavior
I think people will expect something along the lines of,
Additional context
I'm new to storybook, but I have the impression it is the industry standard. Typescript is also industry standard, so I hope to see these technologies play nicely together.
I'm actually struggling to setup storybook in a monorepo (very common in industry today) with typescript and multiple React applications sharing one component library. I want storybook to run in the package for the component library.
The text was updated successfully, but these errors were encountered: