You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No errors or warnings to be thrown. Behavior should be exactly as when using SelectInput inside ReferenceInput. This only appears to be happening when populating the choices via the ReferenceInput. We don't see the messages when hardcoding an array of values in the app. It happens on both the Create and Edit views.
What happened instead:
I get warnings printed in the console, but the App behavior appears to work as it should. (Full stack traces omitted for brevity):
Warning: Failed prop type: The prop `choices` is marked as required in `RadioButtonGroupInput`, but its value is `undefined`.
Warning: React does not recognize the `setFilter` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `setfilter` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Warning: React does not recognize the `setPagination` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `setpagination` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Warning: React does not recognize the `setSort` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `setsort` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
What you were expecting:
No errors or warnings to be thrown. Behavior should be exactly as when using
SelectInput
insideReferenceInput
. This only appears to be happening when populating thechoices
via theReferenceInput
. We don't see the messages when hardcoding an array of values in the app. It happens on both the Create and Edit views.What happened instead:
I get warnings printed in the console, but the App behavior appears to work as it should. (Full stack traces omitted for brevity):
Steps to reproduce:
This code works fine:
This code causes the warning stack traces in the console:
Other information:
Both examples refer to the following resource that is defined in the App.js:
It returns data in this format:
Which is massaged into react-admin's preferred format via a custom dataProvider:
Environment
The text was updated successfully, but these errors were encountered: