This issue is part of a series of feedbacks. I been upgrading the Material-UI solution.
Unfortunately, I had to fork the package in order to reach my goal.
Now, it's time to reconciliation.
The issue
I found that the theme is no longer correctly propagated when we nest more than 2
ThemeProvider. It can be seen in the implementation of create-theme-provider.js.
setState() is never called on the child broadcast after receiving a parent theme update.
This issue is part of a series of feedbacks. I been upgrading the Material-UI solution. Unfortunately, I had to fork the package in order to reach my goal. Now, it's time to reconciliation.
The issue
I found that the theme is no longer correctly propagated when we nest more than 2
ThemeProvider. It can be seen in the implementation ofcreate-theme-provider.js.setState()is never called on the child broadcast after receiving a parent theme update.