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
@storybook/addon-docs: Yet another "No code available" #14463
Comments
I have the same problem (angular 11)
On Docs tab of predefined Stories I see "No code available". The "Show code" button is unlocked after clicking on "Reset controls" or after some switching between Stories. The problem is reproducible on versions 6.2.1-6.2.3. Please help! |
@rwieruch was this ever working for this repo? There's a duplicate issue which I'm unable to find right now, which is that addon-docs sets up the source-loader to run on Ideally it would simply use the |
@shilman Should I create a separate issue? The malfunction in the reference example looks like a bug. |
@pravbeseda that bug already exists here i think #14193 |
Yes, it could be that I changed something in the in my last commits that caused this issue, but I have a hard time narrowing it down. So you are saying that I need to name my stories in a specific way to make it work again? I can look into this! |
@rwieruch this constraint has been there since v5.3, which is that in order for source-loader to be auto-registered by addon-docs you must name your stories files |
Confirmation: Story needs to be named *.story or *.stories. Thanks @shilman 👍🏽 |
using Angular 13.2.5 and Storybook 6.4.19 still not work, my files calling "right" way All stories load correctly but in docs tab show "No code available" when click on some control or "reset control" the code show correctly. maybe is because my project structure?
my .storybook/main.js file
|
I am not sure when this happened, but for
@storybook/addon-docs
I get "No code available". It worked some time ago though.Version: 6.1.21
main.js:
(I tried removing
@storybook/addon-storysource
, as suggested over here, but without success.)┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: