-
Notifications
You must be signed in to change notification settings - Fork 4k
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
DISCUSSION: Use of react-form (problem with prop validations) #856
Comments
Can you please specify the warnings you are seeing that you'd like to go away? I cannot tell from the code which are problematic. |
All warnings that complain that given property (input, meta) does not exists on SUI React Elements. These properties are passed from the wrapping |
In order for us to be able to make code changes that fix the issue, we'll need very specific information. It would be most helpful if you could post the full warning messages that you feel should be removed, then we can assess them and possibly make changes. |
@levithomason For example following:
input and meta are |
Ah, these are built-in React warnings, not ours. React warns anytime you pass an invalid html attribute to a DOM node. In this case, the setup you are using is passing If these are Redux Form props, then Redux Form should be "consuming" them. You are supposed to consume all props your components use, and only pass on extra props. All our components do this and are tested to do so 👍 Unless I'm still missing something here (totally possible!), this issue should be opened on Redux Form. |
Here is one of their issues, noting the same problem with |
Hi. While prop validation surely adds some safety to react components, it also raises several issues. One of the biggest ones is thta components cannot be further extended, for example with redux form as they complain a lot.
For example, this is how naive version of implementing a Select component in redux-form looks like:
And this is what needs to be done in case we want to get rid of warnings:
Any idea how can this be simplified, or just get rid of those warnings?
The text was updated successfully, but these errors were encountered: