Migrate storybook to typescript #2747
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate storybook to typescript and modern Component Story Format (CSF)
.storybookfrom eslint. The storybook config is not included in a tsconfig so eslint will error out. This may be resolved in the future, but its not crucial. Context: error: Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser. typescript-eslint/typescript-eslint#967 (comment)Note: Type checking of stories does not happen at compile time... yet. It is currently incompatible with our version of Babel+Monorepo. This will be enabled in a future PR.