Form validation
We recommend using schema-typed to manage and verify form data. The prompt information provided to the user when there is an error data in the form.
Usage
Step 1: Import Form and Schema.
import { Form, Schema } from 'rsuite';Step 2: Use Schema to define the data model.
const model = Schema.Model({
name: Schema.Types.StringType().isRequired('This field is required.'),
email: Schema.Types.StringType().isEmail('Please enter a valid email address.')
});You can learn more about about
Schemaby reading this guide.
Step 3: Set model for <Form>.
const TextField = ({ name, label, accepter, ...rest }) => (
<Form.Group controlId={name}>
<Form.ControlLabel>{label} </Form.ControlLabel>
<Form.Control name={name} accepter={accepter} {...rest} />
</Form.Group>
);
return (
<Form model={model}>
<TextField name="name" label="Username" />
<TextField name="email" label="Email" />
<Button appearance="primary" type="submit">
Submit
</Button>
</Form>
);Examples
Default check
The form will automatically trigger the data check after the submit event is triggered.
Schema Model
Form Check needs to be used <Form>, <Form.Control> and Schema 。
<Form>To define a form, you can setformValueandmodelfor the form, andmodelis the data model created bySchema.Model.<Form.Control>Define a Filed that corresponds to thekeyof theSchema.Modelobject via thenameproperty. For detailed reference: Custom Form Components.Schema.ModelDefine a data model, using the reference schema.- Custom trigger check:
<Form>instance providescheckandcheckForFieldmethods, used to trigger form checksum field validation
Field level Verification rules
When there are more and more Fields, huge model codes or files are generated. And since in the definition at the top level, it is not flexible enough(ex: If a new Field is added or a Field is deleted, Normally you also need to manipulate the model at the top level)
At this time, the verification rules of the Field level may be a better choice. It adds it when the component is mounted, and delete it when the component is unmounted.
<Form.Control>supports adding verification rule for the current Field via theruleattribute.
Asynchronous check
Under certain conditions, we need to perform asynchronous verification on the data, such as verifying whether the username is duplicated. The following example will illustrate the processing of asynchronous verification.
- Set the
checkAsyncproperty on<Form.Control>that requires asynchronous validation. - The validation rules for asynchronous validation add an object with a return value of Promise via the
addRulemethod ofschema. - The check can be triggered manually by calling
checkAsyncandcheckForFieldAsyncof<Form>.
Custom Form.Control
All Data Entry-related components can be used in forms such as Checkbox, SelectPicker, Slider, and so on. But you need to use the Form.Control component for data management and data association with the Form component.
Form.Controlused to bind data fields in a Form, passing thenameattribute to thekeyof the Schema.Model object.Form.Controlthe default is anInputcomponent, which can be set through the ʻaccepter` component.
Third-Party Libraries
Sometimes you need to customize form components or be compatible with third-party components. For example react-select.
Custom trigger verification
In some cases, there is no need for real-time validation of the form data. You can customize the way the control is validated and configure the checkTrigger parameter.
The default value of checkTrigger is 'change', options includes:
'change': trigger verification when data change'blur': trigger verification when component blur'none': Only valid when calling thecheck()method of<Form>
There are checkTrigger properties on the <Form> and <Form.Control> components. You can define the entire form's validation method in <Form>. If there is a form component that needs to handle the validation independently, you can Set it on <Form.Control>.