2.1.0 ā€¢ Published 4 months ago

@roqueform/react v2.1.0

Weekly downloads
-
License
MIT
Repository
github
Last release
4 months ago

React integration for Roqueform

Hooks and components to integrate Roqueform with React.

npm install --save-prod @roqueform/react

Overview

šŸ”Ž API documentation is available here.

useField hook has the same signature as the createField function:

import type { SyntheticEvent } from 'react';
import { FieldRenderer, useField } from '@roqueform/react';

export const App = () => {
  const planetField = useField({ name: 'Mars' });

  const handleSubmit = (event: SyntheticEvent) => {
    event.preventDefault();

    // Submit the field value
    doSubmit(planetField.value);
  };

  return (
    <form onSubmit={handleSubmit}>

      <FieldRenderer field={planetField.at('name')}>
        {nameField => (
          <input
            type="text"
            value={nameField.value}
            onChange={event => {
              nameField.setValue(event.target.value);
            }}
          />
        )}
      </FieldRenderer>

      <button type="submit">
        {'Submit'}
      </button>

    </form>
  );
};

useField hook returns a Field instance that is preserved between re-renders.

useField();
// ā®• Field

You can provide the initial value for a field.

useField({ planet: 'Mars' });
// ā®• Field<unknown, { planet: string }>

If you pass a callback as an initial value, it would be invoked when the field is initialized.

useField(() => getInitialValue());

Pass a plugin as the second argument of the useField hook.

import { useField } from '@roqueform/react';
import { errorsPlugin } from 'roqueform';

const planetField = useField({ planet: 'Pluto' }, errorsPlugin());

planetField.addError('Too far away');

The FieldRenderer component subscribes to the given field instance and re-renders children when an event is dispatched onto the field:

import { FieldRenderer, useField } from '@roqueform/react';

const App = () => {
  const planetField = useField({ name: 'Mars' });

  return (
    <FieldRenderer field={planetField.at('name')}>
      {nameField => (
        <input
          type="text"
          value={nameField.value}
          onChange={event => {
            nameField.setValue(event.target.value);
          }}
        />
      )}
    </FieldRenderer>
  );
};

When a user updates the input value, the nameField is updated and FieldRenderer component is re-rendered. The single argument of the children render function is the field passed as a field prop to the FieldRenderer component.

Eager and lazy re-renders

Let's consider the form with two FieldRenderer elements. One of them renders the value of the root field and the other one renders an input that updates the child field:

const App = () => {
  const planetField = useField({ name: 'Mars' });

  return <>
    <FieldRenderer field={planetField}>
      {() => JSON.stringify(planetField.value)}
    </FieldRenderer>

    <FieldRenderer field={planetField.at('name')}>
      {nameField => (
        <input
          type="text"
          value={nameField.value}
          onChange={event => {
            nameField.setValue(event.target.value);
          }}
        />
      )}
    </FieldRenderer>
  </>;
};

By default, FieldRenderer component re-renders only when the provided field was updated directly, so updates from ancestors or child fields would be ignored. Add the eagerlyUpdated property to force FieldRenderer to re-render whenever its value was affected.

- <FieldRenderer field={planetField}>
+ <FieldRenderer
+   field={planetField}
+   eagerlyUpdated={true}
+ >
    {() => JSON.stringify(planetField.value)}
  </FieldRenderer>

Now both fields are re-rendered when user edits the input text.

Reacting to changes

You can use an onChange handler that is triggered only when the field value was updated non-transiently.

<FieldRenderer
  field={planetField.at('name')}
  onChange={value => {
    // Handle the non-transient name changes
  }}
>
  {nameField => (
    <input
      type="text"
      value={nameField.value}
      onChange={event => {
        nameField.setValue(event.target.value);
      }}
    />
  )}
</FieldRenderer>
2.1.0

4 months ago

2.0.0

4 months ago

1.1.0

9 months ago

1.0.0

1 year ago