New Field validate prop is passed through to underlying component (React warning)
See original GitHub issueFor example:
<Field
component={TextField}
name="email"
floatingLabelText="Email address"
disabled={submitting}
validate={[required]}
/>
Results in:
Warning: Unknown prop `validate` on <input> tag. Remove this prop from the element.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:7 (1 by maintainers)
Top Results From Across the Web
How to validate React props using PropTypes - LogRocket Blog
Learn how to validate props with React PropTypes, React's internal mechanism for adding type checking to component props.
Read more >[React 15.2.0] Additional props warning · Issue #1249 - GitHub
The unknown-prop warning will fire if you attempt to render a DOM element with a prop that is not recognized by React as...
Read more >How do I add validation to the form in my React component?
class Test extends React.Component { constructor(props) { super(props); this.state = { fields: {}, errors: {}, }; } handleValidation() { let fields ...
Read more >How to Add React Form Validation - Telerik
This article teaches basic React form validation using controlled state inside of components. We use classes and plan to have a follow up ......
Read more >Field - Redux Form
Allows you to to provide a field-level validation rule. The function is given the fields current value, all other form values, the props...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just adding a ‘Me too’ here – getting a warning about passing
validate
down to input, with code like the OPs.This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.