Open segeeslice opened 3 years ago
It appears that eliminating this bug is entirely dependent on updating our material-ui
package, per this Stack Overflow question. Otherwise, we would need to actually go into the material-ui
files and change how they use the findDOMNode()
method.
According to that Stack Overflow, it is updated in v5 which is currently in alpha (status at this link).
So we can either:
StrictMode
entirelyThe second appears to be the most viable solution for now, so as this isn't a breaking bug, so we'll just have to keep watch on it.
Warnings appear when new UI components are rendered without a proper reference. This doesn't seem to affect performance, but it would be useful to look into.
Example warning: