Warning: Received `true` for a non-boolean attribute `loading`.
See original GitHub issueDescribe the bug
At the console: Warning: Received true
for a non-boolean attribute loading
.
To Reproduce Steps to reproduce the behavior:
- vue create my-project
- npx -p @storybook/cli sb init --type vue
- Then follow the doc from https://storybook.js.org/docs/guides/guide-vue/
repo: https://github.com/HiHiPoBang/storybook-demo
Expected behavior No error log
Screenshots
System:
- OS: [MacOS]
- Device: [iMac 2017]
- Browser: [chrome]
- Framework: [vue]
- Addons: [all]
- Version: [5.1.3]
Issue Analytics
- State:
- Created 4 years ago
- Reactions:38
- Comments:34 (12 by maintainers)
Top Results From Across the Web
Warning: Received `false` for a non-boolean attribute. How do ...
This error with styled-components appears to be due to styled() attempting to apply a boolean ...
Read more >How to fix the 'Received "true" for a non-boolean attribute' error
The trick is to use the unary plus operator to convert boolean to number. before your booleans values. According to MDN unary operator...
Read more >Warning: Received true for non-boolean attribute gray . #1198
How can I resolve this warning? Warning: Received `true` for non-boolean attribute `gray`. If this is expected, cast the value to a string....
Read more >How to Fix ' Received false for non-boolean attribute' Errors
The "Warning: Received false for a non-boolean attribute className." warning happens in React when you try to conditionally set a attribute, ...
Read more >Styled-components "Warning Received `true` for non-boolean ...
Ok, first of all, what does this error mean. It means that you passed boolean value for the property of a DOM element....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I get this one as well on React project (Storybook 5.1.3)
I’m on it