Click 'full screen mode' button will raise Failed prop type warning
See original GitHub issueExpected Behavior
no warning in console
Actual Behavior
Warning: Failed prop type: The prop showBranding
is marked as required in StageHeaderComponent
, but its value is undefined
Steps to Reproduce
-
npm start
-
in browser open http://0.0.0.0:8601/
-
click ‘full screen mode’ button above the canvas
-
warning will be displayed in browser console
Operating System and Browser
Mac OS Safari/Chrome/Firefox
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to fix Warning: Failed prop type - reactjs - Stack Overflow
It is really hard to read your code, but it seems that the onChange functions that you are passing to your <input> elements...
Read more >How To Debug React Components Using React Developer ...
Each component will take a prop called show . If show is falsy, the component will return null . The components will consume...
Read more >User and Workspace Settings - Visual Studio Code
Activity Bar display on the left of the editor. Open the Settings Editor ... The error can be as simple as a missing...
Read more >React Hooks cheat sheet: Best practices with examples
Editor's note: This React Hooks tutorial was last updated in January 2021 to include more React Hooks best practices and examples.
Read more >React Box - Material UI - MUI
The Button component defines its own styles. CSS inheritance doesn't help. To workaround the problem, you can use the sx prop directly on...
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
^Thank you for making that connection @thisandagain! Not sure why I didn’t see that yesterday when making the PR.
Woops sorry no it is not a duplicate, my bad!