@achingbrain/react-validation v2.11.1
react-validation
Component to provide simple form validation for React components. It uses the Controlled Components approach for validation.
It is not easy to validate forms with React. The reason is a one-way data flow style. In this case we can't affect forms from the inputs in an easy way. React-validation provides several components which are 'connected' to the form via the input's method attached by the Form component.
DEMO
DEMO src
It is just a validation and doesn't provide any model or something similar. You can use FormData or something like form-serialize to get form data.
NOTE: Always pass the name and validations props. They are required.
Additional markup is allowed inside the Validation.Form markup.
Any additional props (such as event handlers) can also be passed to components.
If you find any bug or error, please feel free to raise an issue. Pull requests are also welcome.
Installation
npm install react-validation
Test
npm run test:dev
Example usage
With @2.*, react-validation is no longer dependent on the external validator. You may use whatever validation strategy you want by extending the rules object.
Let's take a look at its initial state:
export default = {};That's it, just an empty object literal. We don't have any validation rules OOTB because of an extremely high number of possibilities, but it's still recommended to use a well-tested library for known reasons.
So first of all let's extend it and add some rules:
import React from 'react';
// NOTE: Deprecated
import Validation from 'react-validation';
// From v2.10.0
// import { rules, Form, Input, Select, Textarea, Button } from 'react-validation/lib/build/validation.rc'
import validator from 'validator';
// Use Object.assign or any similar API to merge a rules
// NOTE: IE10 doesn't have Object.assign API natively. Use polyfill/babel plugin.
Object.assign(Validation.rules, {
// Key name maps the rule
required: {
// Function to validate value
// NOTE: value might be a number -> force to string
rule: value => {
return value.toString().trim();
},
// Function to return hint
// You may use current value to inject it in some way to the hint
hint: value => {
return <span className='form-error is-visible'>Required</span>
}
},
email: {
// Example usage with external 'validator'
rule: value => {
return validator.isEmail(value);
},
hint: value => {
return <span className='form-error is-visible'>{value} isnt an Email.</span>
}
},
// This example shows a way to handle common task - compare two fields for equality
password: {
// rule function can accept argument:
// components - components registered to Form mapped by name
rule: (value, components) => {
const password = components.password.state;
const passwordConfirm = components.passwordConfirm.state;
const isBothUsed = password
&& passwordConfirm
&& password.isUsed
&& passwordConfirm.isUsed;
const isBothChanged = isBothUsed && password.isChanged && passwordConfirm.isChanged;
if (!isBothUsed || !isBothChanged) {
return true;
}
return password.value === passwordConfirm.value;
},
hint: () => <span className="form-error is-visible">Passwords should be equal.</span>
},
// Define API rule to show hint after API error response
api: {
// We don't need the rule here because we will call the 'showError' method by hand on API error
hint: value => (
<button
className="form-error is-visible"
>
API Error on "{value}" value. Focus to hide.
</button>
)
}
});Now we've added required and email to our rules with provided hints. This might be separated in a file where all the rules are registered.
That's it. We can now use it in our React components:
import Validation from 'react-validation';
import React, {Component, PropTypes} from 'react';
export default class Registration extends Component {
render() {
return <Validation.components.Form>
<h3>Registration</h3>
<div>
<label>
Email*
<Validation.components.Input value='email@email.com' name='email' validations={['required', 'email']}/>
</label>
</div>
<div>
<label>
Password*
<Validation.components.Input type='password' value='' name='password' validations={['required']}/>
</label>
</div>
<div>
<Validation.components.Button>Submit</Validation.components.Button>
</div>
</Validation.components.Form>;
}
}Note the validations prop. It's an array of strings that maps to the rules keys we've extended.
Components and props
react-validation provides a components object that contains Form, Input, Select, area and Button components.
All of them are just custom wrappers around the native components. They can accept any valid attributes and a few extra:
containerClassName-Input,Selectandarea:react-validationwraps the native components with an extra block. This prop adds aclassNameto the wrapper.errorContainerClassName: wrapper's error modifier className.validations-Input,Selectandarea: accepts an array of validations strings that refers to the rules object's keys.errorClassName-Input,Select,Buttonandarea: adds the passed value toclassNameon error occurrences.
NOTE: Always provide a name prop to Input, Select and area. Always pass the validations prop to Input, Select and area.
Form component
Validation.components.FormThe most important component, which provides the heart of react-validation. It basically mixes the binding between the form itself and child react-validation components via context.
Any valid props can easily be passed to Form, such onSubmit and method.
Form provides four public methods:
validate(name)- validates input with the passed name. The difference between this method and default validation is thatvalidatemarks the input asisUsedandisChanged.name- name of the corresponding component.bashowError(name [,hint])- helps to handle async API errors.hint- optional hint to show. Can be string (error key, ex 'required') or function which returns hint (jsx).hideError(name)- hides a corresponding component's error.validateAll()- validates all react-validation components. Returns a map (key: field name prop, value:<Array>non passed validation rules) of invalid fields.
export default class Comment extends Component {
handleSubmit = (event) => {
event.preventDefault();
// Emulate async API call
setTimeout(() => {
// NOTE: 'api' should be defined on 'extend' step
this.form.showError('username', 'api');
}, 1000);
};
removeApiError = () => {
this.form.hideError('username');
};
render() {
return <Validation.components.Form ref={c => { this.form = c }} onSubmit={this.handleSubmit.bind(this)}>
<div className="row">
<div className="small-12 columns">
<h3>Leave a comment</h3>
</div>
</div>
<div className="row">
<div className="small-12 medium-4 columns">
<label>
<Validation.components.Input
onFocus={this.removeApiError}
placeholder="username"
type="text"
errorClassName="is-invalid-input"
containerClassName=""
value="Username"
name="username"
validations={['required', 'alpha']}
/>
</label>
</div>
<div className="small-12 medium-8 columns">
<label>
<Validation.components.Textarea
placeholder="Leave your comment..."
errorClassName="is-invalid-input"
containerClassName=""
value="Comment"
name="comment"
validations={['required']}
/>
</label>
</div>
</div>
<div className="row">
<div className="small-12 medium-6 columns">
<Validation.components.Button className="button">Submit</Validation.components.Button>
</div>
</div>
</Validation.components.Form>
}
}Input component
Validation.components.InputA wrapper around the native input. It accepts a validations prop - an array of strings that refers to rules object keys.
<Validation.components.Input name='firstname' validations={['alpha', 'lt8']}/>NOTE: For types radio and checkbox, react-validation will drop the value to an empty string when it's not checked. This is to avoid validation of non-checked inputs.
react-validation will break with the first listed rule, if more than one rule is broken. In the example above (lt8 - value length less than 8), for really long value with d1g1t input value, the alpha rule will break validation first. We can control it by ordering rules within the validations array.
Textarea component
Validation.components.TextareaA wrapper around the native area. Like Input, it accepts a validations prop. Nothing special here:
<Validation.components.Textarea name='comment' value='' validations={['required']}/>Select component
Validation.components.SelectA wrapper around the native select. Like Input, it accepts a validations prop. Nothing special here:
<Validation.components.Select name='city' value='' validations={['required']}>
<option value=''>Choose your city</option>
<option value='1'>London</option>
<option value='2'>Kyiv</option>
<option value='3'>New York</option>
</Validation.components.Select>Button component
Validation.components.ButtonA wrapper around the native button. React-validation disables (adds disabled prop) the button on error occurrences. This behavior could be suppressed by passing the disabled prop directly to a component.
Custom components
If the components provided by react-validation don't quite fit your needs for markup structure (for instance, you
might want the hint to show before an <input>), you can create your own versions
of input, select, and area. (button and form are simple single-element
components, and shouldn't need further customisation).
Here is an example that would render an <input> according to the Bootstrap
CSS framework:
import React, { Component } from 'react';
import { inputFactory } from 'react-validation/lib/build/validation.rc';
// Not using ES6 classes? Then you'd write instead:
// const MyBootstrapInput = React.createClass(...)
//
// If you are using ES7 decorators, you can use:
// @inputFactory
class MyBootstrapInput extends Component {
render() {
return (
<div className={`form-group ${this.props.hint && 'has-error'} ${this.props.containerClassName}`}>
<label className="control-label" htmlFor={this.props.id}>
{this.props.label}{/* You can use your own props */}
</label>
{/* "onChange", "onBlur", and "value/checked" are important, don't forget them: */}
<input
className={`form-control ${this.props.className}`}
id={this.props.id}
type={this.props.type}
onChange={this.props.onChange}
onBlur={this.props.onBlur}
value={this.props.value}
checked={this.props.checked}
/>
{ this.props.hint && <div className="help-block">{this.props.hint}</div> }
</div>
);
}
}
// Wrap the component in the factory (if not using ES7 decorators)
export default inputFactory(MyBootstrapInput);You can then use your custom component like the other react-validation components:
import BootstrapInput from 'path/to/my/component/file';
<BootstrapInput label="Email" value='email@email.com' name='email' validations={['required', 'email']}/>Migration from 1.*
extendErrors API
extendErrors no longer exists. Replace it with the new approach of validation rules registration. hint appearance is now fully controlled:
Object.assign(Validation.rules, {
required: {
rule: value => {
return value.trim();
},
hint: value => {
return <span className='form-error is-visible'>Required</span>
}
}
});Defaults
React-validation no longer has any defaults. This is TBD but for a 2.0.0 please provide errorClassName and containerClassName directly to the validation components.
Validations
validations prop now accepts an array of strings instead of objects. It's made to be more simple and reduce render code.
Components API moved to Form API. forceValidate method no longer exist.