useForm
useForm
is a hook that allows to manage forms. It has some action
methods that create
, edit
and clone
the form. The hook return value comes to according to the called action and it can run different logic depending on the action
.
You can think of useForm
as a bridge between your state
and dataProvider
. It's a low-level hook that you can use to build your own form components. It's also use notificationProvider
to inform users according to the action
and dataProvider
response.
Let's review how useForm
works behind the scenes.
- create
- edit
- clone
After form is submitted:
useForm
callsonFinish
function with the form values.onFinish
function callsuseCreate
with the form values.useCreate
callsdataProvider
'screate
function and returns the response.useForm
callsonSuccess
oronError
function with the response, depending on the response status.onSuccess
oronError
function then calls theopen
function of thenotificationProvider
to inform the user.useForm
, redirects to thelist
page.
On mount, useForm
calls useGetOne
hook to retrieve the record to be edited. The id
for the record is obtained from the URL
or props
.
After form is submitted:
useForm
callsonFinish
function with the form values.onFinish
function callsuseUpdate
with the form values.useUpdate
callsdataProvider
'supdate
function and returns the response.useForm
callsonSuccess
oronError
function with the response, depending on the response status.onSuccess
oronError
function then calls theopen
function of thenotificationProvider
to inform the user.useForm
, redirects to thelist
page.
On mount, useForm
calls useGetOne
hook to retrieve the record to be edited. The id
for the record is obtained from the URL
or props
.
After form is submitted:
useForm
callsonFinish
function with the form values.onFinish
function callsuseCreate
with the form values.useUpdate
callsdataProvider
'supdate
function and returns the response.useForm
callsonSuccess
oronError
function with the response, depending on the response status.onSuccess
oronError
function then calls theopen
function of thenotificationProvider
to inform the user.useForm
, redirects to thelist
page.
This is the default behavior of useForm
. You can customize it by passing your own redirect
, onFinish
, onMutationSuccess
and onMutationError
props.
useForm
does not manage any state. If you're looking for a complete form library, refine
supports three form libraries out-of-the-box.
- React Hook Form (for Headless users) - Documentation - Example
- Ant Design Form (for Ant Design users) - Documentation - Example
- Mantine Form (for Mantine users) - Documentation - Example
All the data related hooks(useTable, useForm, useList etc.) of refine can be given some common properties like resource
, meta
etc.
Please refer to General Concepts for more information.
Basic Usage
We'll show the basic usage of useForm
by adding an creating form.
import { useState } from 'react'
import { useForm } from '@pankod/refine-core'
const PostCreate = () => {
const [title, setTitle] = useState()
const { onFinish } = useForm({
action: 'create',
})
const onSubmit = (e) => {
e.preventDefault()
onFinish({ title })
}
return (
<form onSubmit={onSubmit}>
<input onChange={(e) => setTitle(e.target.value)} />
<button type="submit">Submit</button>
</form>
)
}
- Returns the
mutationResult
after called theonFinish
callback. - Accepts generic type parameters. It is used to define response type of the mutation and query.
Properties
action
useForm
can handle edit
, create
and clone
actions.
By default, it determines the action
from route.
- If the route is
/posts/create
thus the hook will be called withaction: "create"
. - If the route is
/posts/edit/1
, the hook will be called withaction: "edit"
. - If the route is
/posts/clone/1
, the hook will be called withaction: "clone"
.
It can be overridden by passing the action
prop where it isn't possible to determine the action from the route (e.g. when using form in a modal or using a custom route).
- create
- edit
- clone
action: "create"
is used for creating a new record that didn't exist before.
useForm
uses useCreate
under the hood for mutations on create mode.
In the following example, we'll show how to use useForm
with action: "create"
.
action: "edit"
is used for editing an existing record. It requires the id
for determining the record to edit. By default, it uses the id
from the route. It can be changed with the setId
function or id
property.
It fetches the record data according to the id
with useOne
and returns the queryResult
for you to fill the form. After the form is submitted, it updates the record with useUpdate
.
In the following example, we'll show how to use useForm
with action: "edit"
.
action: "clone"
is used for cloning an existing record. It requires the id
for determining the record to clone. By default, it uses the id
from the route. It can be changed with the setId
function.
You can think action:clone
like save as. It's similar to action:edit
but it creates a new record instead of updating the existing one.
It fetches the record data according to the id
with useOne
and returns the queryResult
for you to fill the form. After the form is submitted, it creates a new record with useCreate
.
In the following example, we'll show how to use useForm
with action: "clone"
.
resource
Default: It reads the
resource
value from the current URL.
It will be passed to the dataProvider
's method as a params. This parameter is usually used to as a API endpoint path. It all depends on how to handle the resource
in your dataProvider
. See the creating a data provider
section for an example of how resource
are handled.
- When
action
is"create"
, it will be passed to thecreate
method from thedataProvider
. - When
action
is"edit"
, it will be passed to theupdate
and thegetOne
method from thedataProvider
. - When
action
is"clone"
, it will be passed to thecreate
and thegetOne
method from thedataProvider
.
useForm({
resource: 'categories',
})
id
id
is used for determining the record to edit
or clone
. By default, it uses the id
from the route. It can be changed with the setId
function or id
property.
It is useful when you want to edit
or clone
a resource
from a different page.
Note:
id
is required whenaction: "edit"
oraction: "clone"
.
useForm({
action: 'edit', // or clone
resource: 'categories',
id: 1, // <BASE_URL_FROM_DATA_PROVIDER>/categories/1
})
redirect
redirect
is used for determining the page to redirect after the form is submitted. By default, it uses the list
. It can be changed with the redirect
property.
It can be set to "show" | "edit" | "list" | "create"
or false
to prevent the page from redirecting to the list page after the form is submitted.
useForm({
redirect: false,
})
onMutationSuccess
It's a callback function that will be called after the mutation is successful.
It receives the following parameters:
data
: Returned value fromuseCreate
oruseUpdate
depending on theaction
.variables
: The variables passed to the mutation.context
: react-query context.
useForm({
onMutationSuccess: (data, variables, context) => {
console.log({ data, variables, context })
},
})
onMutationError
It's a callback function that will be called after the mutation is failed.
It receives the following parameters:
data
: Returned value fromuseCreate
oruseUpdate
depending on theaction
.variables
: The variables passed to the mutation.context
: react-query context.
useForm({
onMutationError: (data, variables, context) => {
console.log({ data, variables, context })
},
})
invalidates
You can use it to manage the invalidations that will occur at the end of the mutation.
By default it's invalidates following queries from the current resource
:
- on
"create"
or"clone"
mode:"list"
and"many"
- on
"edit"
mode:"list"
","many"
and"detail"
useForm({
invalidates: ['list', 'many', 'detail'],
})
dataProviderName
If there is more than one dataProvider
, you should use the dataProviderName
that you will use.
It is useful when you want to use a different dataProvider
for a specific resource.
If you want to use a different dataProvider
on all resource pages, you can use the dataProvider
prop of the <Refine>
component.
useForm({
dataProviderName: 'second-data-provider',
})
mutationMode
Mutation mode determines which mode the mutation runs with. Mutations can run under three different modes: pessimistic
, optimistic
and undoable
. Default mode is pessimistic
.
Each mode corresponds to a different type of user experience.
For more information about mutation modes, please check Mutation Mode documentation page.
useForm({
mutationMode: 'undoable', // "pessimistic" | "optimistic" | "undoable",
})
successNotification
NotificationProvider
is required for this prop to work.
After form is submitted successfully, useForm
will call open
function from NotificationProvider
to show a success notification. With this prop, you can customize the success notification.
useForm({
successNotification: (data, values, resource) => {
return {
message: `Post Successfully created with ${data.title}`,
description: 'Success with no errors',
type: 'success',
}
},
})
errorNotification
NotificationProvider
is required for this prop to work.
After form is submit is failed, useForm
will call open
function from NotificationProvider
to show a success notification. With this prop, you can customize the success notification.
useForm({
errorNotification: (data, values, resource) => {
return {
message: `Something went wrong when deleting ${data.id}`,
description: 'Error',
type: 'error',
}
},
})
{
"message": "Error when updating <resource-name> (status code: ${err.statusCode})" or "Error when creating <resource-name> (status code: ${err.statusCode})",
"description": "Error",
"type": "error",
}
metaData
metaData
is used following two purposes:
- To pass additional information to data provider methods.
- Generate GraphQL queries using plain JavaScript Objects (JSON). Please refer GraphQL for more information.
In the following example, we pass the headers
property in the metaData
object to the create
method. With similar logic, you can pass any properties to specifically handle the data provider methods.
useForm({
metaData: {
headers: { 'x-meta-data': 'true' },
},
})
const myDataProvider = {
//...
create: async ({ resource, variables, metaData }) => {
const headers = metaData?.headers ?? {}
const url = `${apiUrl}/${resource}`
const { data } = await httpClient.post(url, variables, { headers })
return {
data,
}
},
//...
}
queryOptions
Works only in
action: "edit"
oraction: "clone"
mode.
in edit
or clone
mode, refine uses useOne
hook to fetch data. You can pass queryOptions
options by passing queryOptions
property.
useForm({
queryOptions: {
retry: 3,
},
})
createMutationOptions
This option is only available when
action: "create"
oraction: "clone"
.
In create
or clone
mode, refine uses useCreate
hook to create data. You can pass mutationOptions
by passing createMutationOptions
property.
useForm({
createMutationOptions: {
retry: 3,
},
})
updateMutationOptions
This option is only available when
action: "edit"
.
In edit
mode, refine uses useUpdate
hook to update data. You can pass mutationOptions
by passing updateMutationOptions
property.
useForm({
updateMutationOptions: {
retry: 3,
},
})
liveMode
Whether to update data automatically ("auto") or not ("manual") if a related live event is received. It can be used to update and show data in Realtime throughout your app. For more information about live mode, please check Live / Realtime page.
useForm({
liveMode: 'auto',
})
onLiveEvent
The callback function that is executed when new events from a subscription are arrived.
useForm({
onLiveEvent: (event) => {
console.log(event)
},
})
liveParams
Params to pass to liveProvider's subscribe method.
Return Values
queryResult
If the action
is set to "edit"
or "clone"
or if a resource
with an id
is provided, useForm
will call useOne
and set the returned values as the queryResult
property.
const { queryResult } = useForm()
const { data } = queryResult
mutationResult
When in "create"
or "clone"
mode, useForm
will call useCreate
. When in "edit"
mode, it will call useUpdate
and set the resulting values as the mutationResult
property."
const { mutationResult } = useForm()
const { data } = mutationResult
setId
useForm
determine id
from the router. If you want to change the id
dynamically, you can use setId
function.
const { id, setId } = useForm()
const handleIdChange = (id: string) => {
setId(id)
}
return (
<div>
<input value={id} onChange={(e) => handleIdChange(e.target.value)} />
</div>
)
redirect
"By default, after a successful mutation, useForm
will redirect
to the "list"
page. To redirect to a different page, you can either use the redirect
function to programmatically specify the destination, or set the redirect property in the hook's options.
In the following example we will redirect to the "show"
page after a successful mutation.
const { onFinish, redirect } = useForm()
// --
const handleSubmit = async (e: React.FormEvent<HTMLFormElement>) => {
e.preventDefault()
const data = await onFinish(formValues)
redirect('show', data?.data?.id)
}
// --
onFinish
onFinish
is a function that is called when the form is submitted. It will call the appropriate mutation based on the action
property.
You can override the default behavior by passing an onFinish
function in the hook's options.
For example you can change values before sending to the API.
formLoading
Loading state of a modal. It's true
when useForm
is currently being submitted or data is being fetched for the "edit"
or "clone"
mode.
FAQ
How can Invalidate other resources?
You can invalidate other resources with help of useInvalidate
hook.
It is useful when you want to invalidate
other resources don't have relation with the current resource.
import { useInvalidate, useForm } from '@pankod/refine-core'
const PostEdit = () => {
const invalidate = useInvalidate()
useForm({
onMutationSuccess: (data, variables, context) => {
invalidate({
resource: 'users',
invalidates: ['resourceAll'],
})
},
})
// ---
}
How can I change the form data before submitting it to the API?
You may need to modify the form data before it is sent to the API.
For example, Let's send the values we received from the user in two separate inputs, name
and surname
, to the API as fullName
.
import React, { useState } from 'react'
import { useForm } from '@pankod/refine-core'
export const UserCreate: React.FC = () => {
const [name, setName] = useState()
const [surname, setSurname] = useState()
const { onFinish } = useForm()
const onSubmit = (e) => {
e.preventDefault()
const fullName = `${name} ${surname}`
onFinish({
fullName: fullName,
name,
surname,
})
}
return (
<form onSubmit={onSubmit}>
<input onChange={(e) => setName(e.target.value)} />
<input onChange={(e) => setSurname(e.target.value)} />
<button type="submit">Submit</button>
</form>
)
}
API Reference
Properties
*
: These props have default values inRefineContext
and can also be set on <Refine> component.useForm
will use what is passed to<Refine>
as default but a local value will override it.
Type Parameters
Property | Desription | Default |
---|---|---|
TData | Result data of the query that extends BaseRecord | BaseRecord |
TError | Custom error object that extends HttpError | HttpError |
TVariables | Values for params. | {} |
Return values
Property | Description | Type |
---|---|---|
onFinish | Triggers the mutation | (values: TVariables) => Promise<CreateResponse<TData> | UpdateResponse<TData> | void > |
queryResult | Result of the query of a record | QueryObserverResult<T> |
mutationResult | Result of the mutation triggered by calling onFinish | UseMutationResult<T> |
formLoading | Loading state of form request | boolean |
id | Record id for clone and create action | BaseKey |
setId | id setter | Dispatch<SetStateAction< string | number | undefined>> |
redirect | Redirect function for custom redirections | (redirect: "list" |"edit" |"show" |"create" | false ,idFromFunction?: BaseKey |undefined ) => data |
Example
npm create refine-app@latest -- --example form-core-use-form