-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Broken @storybook/addon-contexts types #9639
Comments
Same issue for me |
Using import { withContexts } from '@storybook/addon-contexts/dist/preview/frameworks/react'; Works, but then TypeScript can't determine the type of the |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
I'd expect a way to get correct types without knowing internal structure of the library... |
Looking to replace Open PR, API still under consideration: #10028 |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
Describe the bug
Types for
@storybook/addon-contexts@5.3.9
seem to be broken, causing following TypeScript error:To Reproduce
import { withContexts } from '@storybook/addon-contexts/react';
Expected behavior
No errors
The text was updated successfully, but these errors were encountered: