Storybook: 5.1.9 Reproduce 聽#7049 issue; Warning: Received `false` for a non-boolean attribute `loading`.

Created on 28 Jun 2019  路  14Comments  路  Source: storybookjs/storybook

Describe the bug
click sidebar get more menu icon button; at the console: Warning: Received false for a non-boolean attribute loading.

To Reproduce
Steps to reproduce the behavior:

  1. npm i @storybook/react @types/storybook__react @storybook/addon-actions
  2. Then follow the doc from https://storybook.js.org/docs/configurations/typescript-config/
  3. run start-storybook
  4. click sidebar more menu icon button
  5. See error

Expected behavior
show stories and no error

Screenshots
image

System:

  • OS: [MacOS]
  • Device: [Macbook Pro 2016]
  • Browser: [Chrome]
  • Framework: [React, Typescript]
  • Addons: [action]
  • Version: [5.1.9]
bug ui

Most helpful comment

Same here, also using Macbook, Chrome and React

All 14 comments

Same here, also using Macbook, Chrome and React

Same here with Windows 10 and Chrome.

Why is this closed. I'm still getting this bug on v 5.1.9.

@ckwong90 it's not closed?

Hes referencing #7049

I'm still getting the same error in 5.1.9

I took a look; but I was unable to reproduce this on master on both the official storybook example as well as the cra-ts example.

@shilman is the npm release behind on master?

@ndelangen Ironically, I couldn't reproduce this issue when this one came up. But somehow I could reproduce now. It looks like I could fix this one maybe. Can I take it? I'll make a PR in a few hours(I need to go home first haha)

It's yours! 馃

@ndelangen what do you mean?

My question was:
Is what's on master, equal to what's on npm, right now?

Yes AFAIK with the exception of a handful of documentation fixes. Also there are some patch PRs on next that haven't been applied back to master yet. Why do you ask?

Zoinks!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.2.0-beta.10 containing PR #7548 that references this issue. Upgrade today to try it out!

You can find this prerelease on the @next NPM tag.

Closing this issue. Please re-open if you think there's still more to do.

In my case, it was the cookies. Removed all cookies and all cached storage, and automagically Addons tab shows again!

Was this page helpful?
0 / 5 - 0 ratings