[Docs] Add new muiTheme setup requirements to docs + readme
See original GitHub issueProblem Description
Yopp guys,
After updated to latest version (MUI = 0.15.0-beta.1, react, react-dom = 15.0.1), I caught several errors from my inspector :
- Warning: Failed Context Types: Required context
muiTheme
was not specified inPaper
. - Uncaught TypeError: Cannot read property ‘prepareStyles’ of undefined
- Uncaught TypeError: Cannot read property ‘__reactInternalInstance$f2gyonourkjfu80wspjh5mi’ of null
Any tips help me escape from these bugs weirdo ?
Be grateful for your reply.
Versions
- Material-UI: 0.15.0-beta.1
- React: 15.0.1
- Browser: Chrome ver. 49
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:17 (7 by maintainers)
Top Results From Across the Web
[Docs] Add new muiTheme setup requirements to ... - GitHub
Problem Description Yopp guys, After updated to latest version (MUI = 0.15.0-beta.1, ... [Docs] Add new muiTheme setup requirements to docs + readme...
Read more >Intro to ReadMe - ReadMe Documentation
Each developer hub that you publish on ReadMe is considered a project. In your project, your team can add an interactive API reference,...
Read more >ReadMe Documentation
Getting Started With ReadMe. Our knowledge base of everything you'll need to build your beautiful, interactive, and personalized developer hub. PRODUCT GUIDES.
Read more >Manual API Editor - ReadMe Documentation
Go to the Reference Docs tab and add a page like you normally would. On the top-left, there is a dropdown button. This...
Read more >Best Practices - ReadMe Documentation
ReadMe offers a few different formats for documentation in your hub: API ... have more specific requirements for how your documentation looks, you...
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 Free
Top 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
This is problematic when writing tests for pure components which don’t really care about the theme. Is there a suggestion for how to solve this?
Instead of this:
I want to do this:
@newoga We need to make this loud and clear in the README/docs