Managing form state in React can be a bit unwieldy sometimes. There are plenty of great solutions already available that make managing forms state a breeze. However, many of those solutions are opinionated, packed with tons of features that may end up not being used, and/or require shipping a few extra bytes!
Luckily, the recent introduction of React Hooks and the ability to write custom hooks have enabled new possibilities when it comes sharing state logic. Form state is no exception!
react-use-form-state is a small React Hook that attempts to simplify managing form state, using the native form input elements you are familiar with!
To get it started, add react-use-form-state to your project:
npm install --save react-use-form-state
Please note that react-use-form-state requires react@^16.8.0 as a peer dependency.
import { useFormState } from 'react-use-form-state';
export default function SignUpForm({ onSubmit }) {
const [formState, { text, email, password, radio }] = useFormState();
function handleSubmit(e) {
// ...
}
return (
<form onSubmit={handleSubmit}>
<input {...text('name')} />
<input {...email('email')} required />
<input {...password('password')} required minLength="8" />
<input {...radio('plan', 'free')} />
<input {...radio('plan', 'premium')} />
</form>
);
}From the example above, as the user fills in the form, the formState object will look something like this:
{
values: {
name: 'Mary Poppins',
email: 'mary@example.com',
password: '1234',
plan: 'free',
},
touched: {
name: true,
email: true,
password: true,
plan: true,
},
validity: {
name: true,
email: true,
password: false,
plan: true,
},
errors: {
password: 'Please lengthen this text to 8 characters or more',
},
clear: Function,
clearField: Function,
setField: Function,
}useFormState takes an initial state object with keys matching the names of the inputs.
export default function RentCarForm() {
const [formState, { checkbox, radio, select }] = useFormState({
trip: 'roundtrip',
type: ['sedan', 'suv', 'van'],
});
return (
<form>
<select {...select('trip')}>
<option value="roundtrip">Same Drop-off</option>
<option value="oneway">Different Drop-off</option>
</select>
<input {...checkbox('type', 'sedan')} />
<input {...checkbox('type', 'suv')} />
<input {...checkbox('type', 'van')} />
<button>Submit</button>
</form>
);
}useFormState supports a variety of form-level event handlers that you could use to perform certain actions:
export default function RentCarForm() {
const [formState, { email, password }] = useFormState(null, {
onChange(e, stateValues, nextStateValues) {
const { name, value } = e.target;
console.log(`the ${name} input has changed!`);
},
});
return (
<>
<input {...text('username')} />
<input {...password('password')} />
</>
);
}useFormState provides a quick and simple API to get started with building a from and managing its state. It also supports HTML5 form validation out of the box.
<input {...password('password')} required minLength="8" />While this covers that majority of validation cases, there are times when you need to attach custom event handlers or perform custom validation.
For this, all input functions provide an alternate API that allows you attach input-level event handlers such as onChange and onBlur, as well as providing custom validation logic.
export default function SignUpForm() {
const [state, { text, password }] = useFormState();
return (
<>
<input {...text('username')} required />
<input
{...password({
name: 'password',
onChange: e => console.log('password input changed!'),
onBlur: e => console.log('password input lost focus!'),
validate: (value, values, e) => validatePassword(value),
validateOnBlur: true,
})}
/>
</>
);
};The example above demonstrates how you can determine the validity of an input by passing a validate() method. You can also specify custom validation errors using the same method.
The input is considered valid if this method returns true or undefined.
Any truthy value other than true returned from this method will make the input invalid. This returned value is used as a custom validation error that can be retrieved from state.errors.
For convenience, empty collection values such as empty objects, empty arrays, empty maps, empty sets are not considered invalidation errors, and if returned the input will be valid.
<input
{...password({
name: 'password',
// can also return objects, arrays, etc, for more complex error objects
validate: (value, values, event) => {
if (!value.trim()) {
return 'Password is required';
}
if (!STRONG_PASSWORD_REGEX.test(value)) {
return 'Password is not strong enough';
}
},
})}
/>If the input's value is invalid based on the rules specified above, the form state will look similar to this:
{
validity: {
password: false,
},
errors: {
password: 'Password is not strong enough',
}
}If the validate() method is not specified, useFormState will fallback to the HTML5 constrains validation to determine the validity of the input along with the appropriate error message.
useFormState is not limited to actual forms. It can be used anywhere inputs are used.
function LoginForm({ onSubmit }) {
const [formState, { email, password }] = useFormState();
return (
<div>
<input {...email('email')} required />
<input {...password('password')} required minLength="8" />
<button onClick={() => onSubmit(formState)}>Login</button>
</div>
);
}As a convenience, useFormState provides an optional API that helps with pairing a label to a specific input.
When formOptions.withIds is enabled, a label can be paired to an input by using input.label(). This will populate the label's htmlFor attribute for an input with the same parameters.
const [formState, { label, text, radio }] = useFormState(initialState, {
withIds: true, // enable automatic creation of id and htmlFor props
});
return (
<form>
<label {...label('name')}>Full Name</label>
<input {...text('name')} />
<label {...label('plan', 'free')}>Free Plan</label>
<input {...radio('plan', 'free')} />
<label {...label('plan', 'premium')}>Premium Plan</label>
<input {...radio('plan', 'premium')} />
</form>
);Note that this will override any existing id prop if specified before calling the input functions. If you want the id to take precedence, it must be passed after calling the input types like this:
<input {...text('username')} id="signup-username" />useFormState provides a raw type for working with controls that do not use React's SyntheticEvent system. For example, controls like react-select or react-datepicker have onChange and value props that expect a custom value instead of an event.
To use this, your custom component should support an onChange() event which takes the value as a parameter, and a value prop which is expected to contain the value. Note that if no initial value is given, the component will receive a value prop of an empty string, which might not be what you want. Therefore, you must provide an initial value for raw() inputs when working with custom controls.
import DatePicker from 'react-datepicker';
function Widget() {
const [formState, { raw }] = userFormState({ date: new Date() });
return (
<>
<DatePicker {...raw('date')} />
</>
);
}You can also provide an onChange option with a return value in order to map the value passed from the custom control's onChange to a different value in the form state.
function Widget() {
const [formState, { raw }] = userFormState({ date: new Date() });
return (
<>
<DatePicker
{...raw({
name: 'date',
onChange: date => date.toString();
})}
value={new Date(formState.date)}
/>
</>
);
}Note that onChange() for a raw value must return a value.
Many raw components do not support onBlur() correctly. For these components, you can use touchOnChange to mark a field as touched when it changes instead of on blur:
function Widget() {
const [formState, { raw }] = userFormState({ date: new Date() });
return (
<>
<CustomComponent
{...raw({
name: 'date',
touchOnChange: true
})}
/>
</>
);
}There are cases where you may want to update the value of an input manually without user interaction. To do so, the formState.setField method can be used.
function Form() {
const [formState, { text }] = useFormState();
function setNameField() {
// manually setting the value of the "name" input
formState.setField('name', 'Mary Poppins');
}
return (
<>
<input {...text('name')} readOnly />
<button onClick={setNameField}>Set Name</button>
</>
)
}Please note that when formState.setField is called, any existing errors that might have been set due to previous interactions from the user will be cleared, and both of the validity and the touched states of the input will be set to true.
It's also possible to clear a single input's value using formState.clearField.
All fields in the form can be cleared all at once at any time using formState.clear.
function Form() {
const [formState, { text, email }] = useFormState();
return (
<>
<input {...text("first_name")} />
<input {...text("last_name")} />
<input {...email("email")} />
<button onClick={formState.clear}>Clear All Fields</button>
</>
);
}When working with TypeScript, the compiler needs to know what values and inputs useFormState is expected to be working with.
For this reason, useFormState accepts an optional type argument that defines the state of the form and its fields which you could use to enforce type safety.
interface LoginFormFields {
username: string;
password: string;
remember_me: boolean;
}
const [formState, { text }] = useFormState<LoginFormFields>();
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
// OK
<input {...text('username')} />
formState.values.username
// Error
formState.values.doesNotExist
<input {...text('doesNotExist')} />By default, useFormState will use the type any for the form state and its inputs if no type argument is provided. Therefore, it is recommended that you provide one.
By default, the errors property will contain strings. If you return complex error objects from custom validation, you can provide an error type:
interface I18nError {
en: string;
fr: string;
}
interface LoginFormErrors {
username?: string | I18nError;
password?: string;
}
const [formState, { text }] = useFormState<LoginFormFields, LoginFormErrors>();
formState.errors.username; // Will be undefined, a string, or an I18nError.import { useFormState } from 'react-use-form-state';
function FormComponent()
const [formState, inputs] = useFormState(initialState, formOptions);
return (
// ...
)
}useFormState takes an optional initial state object with keys as the name property of the form inputs, and values as the initial values of those inputs (similar to defaultValue/defaultChecked).
useFormState also accepts an optional form options object as a second argument with following properties:
A function that gets called upon any blur of the form's inputs. This functions provides access to the input's blur SyntheticEvent
const [formState, inputs] = useFormState(null, {
onBlur(e) {
// accessing the inputs target that triggered the blur event
const { name, value, ...target } = e.target;
}
});A function that gets triggered upon any change of the form's inputs, and before updating formState.
This function gives you access to the input's change SyntheticEvent, the current formState, the next state after the change is applied.
const [formState, inputs] = useFormState(null, {
onChange(e, stateValues, nextStateValues) {
// accessing the actual inputs target that triggered the change event
const { name, value, ...target } = e.target;
// the state values prior to applying the change
formState.values === stateValues; // true
// the state values after applying the change
nextStateValues;
// the state value of the input. See Input Types below for more information.
nextStateValues[name];
}
});A function that gets called after an input inside the form has lost focus, and is marked as touched. It will be called once throughout the component life cycle. This functions provides access to the input's blur SyntheticEvent.
const [formState, inputs] = useFormState(null, {
onTouched(e) {
// accessing the inputs target that triggered the blur event
const { name, value, ...target } = e.target;
}
});A function that gets called after calling formState.clear indicating that all fields in the form state are cleared successfully.
const [formState, inputs] = useFormState(null, {
onClear() {
// form state was cleared successfully
}
});
formState.clear(); // clearing the form stateIndicates whether useFormState should generate and pass an id attribute to its fields. This is helpful when working with labels.
It can be one of the following:
A boolean indicating whether input types should pass an id attribute to the inputs (set to false by default).
const [formState, inputs] = useFormState(null, {
withIds: true,
});Or a custom id formatter: a function that gets called with the input's name and own value, and expected to return a unique string (using these parameters) that will be as the input id.
const [formState, inputs] = useFormState(null, {
withIds: (name, ownValue) =>
ownValue ? `MyForm-${name}-${ownValue}` : `MyForm-${name}`,
});Note that when withIds is set to false, applying input.label() will be a no-op.
The return value of useFormState. An array of two items, the first is the form state, and the second an input types object.
The first item returned by useFormState.
const [formState, inputs] = useFormState();An object containing the form state that updates during subsequent re-renders. It also include methods to update the form state manually.
formState = {
// an object holding the values of all input being rendered
values: {
[name: string]: string | string[] | boolean,
},
// an object indicating whether the value of each input is valid
validity: {
[name: string]?: boolean,
},
// an object holding all errors resulting from input validations
errors: {
[name: string]?: any,
},
// an object indicating whether the input was touched (focused) by the user
touched: {
[name: string]?: boolean,
},
// clears all fields in the form
clear(): void,
// clears the state of an input
clearField(name: string): void,
// updates the value of an input
setField(name: string, value: string): void,,
}The second item returned by useFormState.
const [formState, input] = useFormState();An object with keys as input types. Each type is a function that returns the appropriate props that can be spread on the corresponding input.
The following types are currently supported:
| Type and Usage | State Shape |
|---|---|
<input {...input.email(name: string)} /> |
{ [name: string]: string } |
<input {...input.color(name: string)} /> |
{ [name: string]: string } |
<input {...input.password(name: string)} /> |
{ [name: string]: string } |
<input {...input.text(name: string)} /> |
{ [name: string]: string } |
<input {...input.url(name: string)} /> |
{ [name: string]: string } |
<input {...input.search(name: string)} /> |
{ [name: string]: string } |
<input {...input.number(name: string)} /> |
{ [name: string]: string } |
<input {...input.range(name: string)} /> |
{ [name: string]: string } |
<input {...input.tel(name: string)} /> |
{ [name: string]: string } |
<input {...input.radio(name: string, ownValue: string)} /> |
{ [name: string]: string } |
<input {...input.checkbox(name: string, ownValue: string)} /> |
{ [name: string]: Array<string> } |
<input {...input.checkbox(name: string)} /> |
{ [name: string]: boolean } |
<input {...input.date(name: string)} /> |
{ [name: string]: string } |
<input {...input.month(name: string)} /> |
{ [name: string]: string } |
<input {...input.week(name: string)} /> |
{ [name: string]: string } |
<input {...input.time(name: string)} /> |
{ [name: string]: string } |
<select {...input.select(name: string)} /> |
{ [name: string]: string } |
<select {...input.selectMultiple(name: string)} /> |
{ [name: string]: Array<string> } |
<textarea {...input.textarea(name: string)} /> |
{ [name: string]: string } |
<label {...input.label(name: string, value?: string)} /> |
N/A – input.label() is stateless and thus does not affect the form state |
<CustomControl {...input.raw(name: string)} /> |
{ [name: string]: any } |
Alternatively, input type functions can be called with an object as the first argument. This object is used to extend the functionality of the input. This includes attaching event handlers and performing input-level custom validation.
<input
{...input.text({
name: 'username',
validate: value => validateUsername(value),
validateOnBlur: true,
})}
/>The following options can be passed:
| key | Description |
|---|---|
name: string |
Required. The name of the input. |
value: string |
The input's own value. Only required by the radio input, and optional for the checkbox input. |
onChange(e): void |
Optional. A change event handler that gets passed the input's change SyntheticEvent. |
onBlur(e): void |
Optional. A blur event handler that gets passed the input's blur SyntheticEvent. |
validate(value: string, values: StateValues, event: Event): any |
Optional. An input validation function that determines whether the input value is valid. It gets passed the input value, all input values in the form, and the change/blur event (or the raw value of the control in the case of .raw()). The input is considered valid if this method returns true or undefined. Any truthy value other than true returned from this method will make the input invalid. Such values are used a custom validation errors that can be retrieved from state.errors. HTML5 validation rules are ignored when this function is specified. |
validateOnBlur: boolean |
Optional. false by default. When set to true and the validate function is provided, the function will be called when the input loses focus. If not specified, the validate function will be called on value change. |
touchOnChange: boolean |
Optional. false by default. When false, the input will be marked as touched when the onBlur() event handler is called. For custom controls that do not support onBlur, setting this to true will make it so inputs will be marked as touched when onChange() is called instead. |
MIT