-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
React does not recognize the hasCreate
prop on a DOM element.
#9108
Comments
Thanks for this report. I don't really understand how you can run into this issue with the code you provided, since it doesn't set In any case, there's a good chance this issue will be fixed by #9101 once it is released. |
EDIT: my bad, actually #9101 cleans other props but not this one which is still needed for some advanced cases including an EE component. But still, I would require a reproduction sandbox, as I did not reproduce in our simple example. |
No news for some time, closing. |
Hi, This is not solved.
this is because when custom actions are not provided, the Default is used (https://github.com/marmelab/react-admin/blob/master/packages/ra-ui-materialui/src/list/ListActions.tsx) which "eats" the hasCreate prop and it is not passed to the TopToolbar The way around this is to create a custom component (like in the docs) but it would be nice to be able to specify actions inline without needing a component
|
Indeed @ruslantalpa , with these instructions I was able to reproduce. Thanks. |
What happened:
When using a
List
element I get this in the console:Steps to reproduce:
Use
List
element like this:Environment
The text was updated successfully, but these errors were encountered: