-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ButtonBase didn't accept function as component property #15823
Comments
Please check your console. There should be multiple warnings. One of which links to https://material-ui.com/guides/composition/#caveat-with-refs |
|
EDIT tl;dr I'm currently upgrading to v4 and this issue has presented itself. If I use a React Router
|
@eps1lon thanks, the ref prop on a |
Not sure what you're referring to. The documented fix doesn't use |
My code sample - I was using the incorrect prop name. All good, code working now. |
In upgrading material v3.9.3 to v4.0.0 error happens. The error happens only in v4.0.0.
I am trying to pass NavLink component to Tab.
ButtonBase.js:142 Uncaught (in promise) Error: Material-UI: expected an Element but found null. Please check your console for additional warnings and try fixing those. If the error persists please file an issue.
Wrapping NavLink with class component resolve this issue.
The text was updated successfully, but these errors were encountered: