Edit
<Edit> provides us a layout for displaying the page. It does not contain any logic but adds extra functionalities like a refresh button.
We will show what <Edit> does using properties with examples.
TIP
The example above shows how to use the resource prop when the component is rendered on a custom page with a different route than the resource route.
If you have multiple resources with the same name, you can pass the identifier instead of the name of the resource. It will only be used as the main matching key for the resource, data provider methods will still work with the name of the resource defined in the <Refine/> component.
For more information, refer to the
identifiersection of the<Refine/>component documentation →
You can swizzle this component to customize it with the Refine CLI
Properties
title
title allows you to add a title inside the <Edit> component. If you don't pass title props, it uses the "Edit" prefix and the singular resource name by default. For example, for the "posts" resource, it will be "Edit post".
saveButtonProps
The <Edit> component has a save button that submits the form by default. If you want to customize this button you can use the saveButtonProps property:
For more information, refer to the
<SaveButton>documentation →
canDelete and deleteButtonProps
canDelete allows you to add a delete button inside the <Edit> component. This button uses the useDelete method provided by the dataProvider
If you want to customize this button you can use the deleteButtonProps property like the code below.
For more information, refer to the
<DeleteButton>documentation →
For more information, refer to the
usePermissiondocumentation →
resource
The <Edit> component reads the resource information from the route by default. If you want to use a custom resource for the <Edit> component, you can use the resource prop:
TIP
The example above shows how to use the resource prop when the component is rendered on a custom page with a different route than the resource route.
If you have multiple resources with the same name, you can pass the identifier instead of the name of the resource. It will only be used as the main matching key for the resource, data provider methods will still work with the name of the resource defined in the <Refine/> component.
For more information, refer to the
identifiersection of the<Refine/>component documentation →
recordItemId
The <Edit> component reads the id information from the route by default. When it cannot be read from the URL, which happens when it's used on a custom page, modal or drawer, recordItemId is used.
The <Edit> component needs the id information for the <RefreshButton> to work properly.
mutationMode
Determines which mode mutation will have while executing <DeleteButton> .
For more information, refer to the mutation mode documentation →
dataProviderName
If not specified, Refine will use the default data provider. If you have multiple data providers, you can use the dataProviderName property to specify which one you want to use:
import { Refine } from "@refinedev/core";
import dataProvider from "@refinedev/simple-rest";
import { Edit } from "@refinedev/antd";
const PostEdit = () => {
return <Edit dataProviderName="other">...</Edit>;
};
export const App: React.FC = () => {
return (
<Refine
dataProvider={{
default: dataProvider("https://api.fake-rest.refine.dev/"),
other: dataProvider("https://other-api.fake-rest.refine.dev/"),
}}
>
{/* ... */}
</Refine>
);
};
goBack
To customize the back button or to disable it, you can use the goBack property:
If your route has no :action parameter or your action is list, the back button will not be shown even if you pass a goBack property. You can override this behavior by using the headerProps property:
import { useBack } from "@refinedev/core";
import { Edit } from "@refinedev/antd";
import { Button } from "antd";
const PostEdit: React.FC = () => {
const back = useBack();
const BackButton = () => <Button>←</Button>;
return (
<Edit goBack={<BackButton />} headerProps={{ onBack: back }}>
<p>Rest of your page here</p>
</Edit>
);
};
isLoading
To toggle the loading state of the <Edit/> component, you can use the isLoading property:
breadcrumb Globally ConfigurableThis value can be configured globally. Click to see the guide for more information.
To customize or disable the breadcrumb, you can use the breadcrumb property. By default the Breadcrumb component from the @refinedev/antd package is used for breadcrumbs.
For more information, refer to the
Breadcrumbdocumentation →
wrapperProps
You can use the wrapperProps property if you want to customize the wrapper of the <Edit/> component. The @refinedev/antd wrapper elements are simply <div/>s and wrapperProps and can get every attribute that <div/> can get.
headerProps
You can use the headerProps property to customize the header of the <Edit/> component:
For more information, refer to the
PageHeaderdocumentation →
contentProps
You can use the contentProps property to customize the content of the <Edit/> component:
For more information, refer to the
Carddocumentation →
headerButtons
By default, the <Edit/> component has a <ListButton> and a <RefreshButton> at the header.
You can customize the buttons at the header by using the headerButtons property. It accepts React.ReactNode or a render function ({ defaultButtons, refreshButtonProps, listButtonProps }) => React.ReactNode which you can use to keep the existing buttons and add your own.
If the "list" resource is not defined, the <ListButton> will not render and listButtonProps will be undefined.
Or, instead of using the defaultButtons, you can create your own buttons. If you want, you can use refreshButtonProps and listButtonProps to utilize the default values of the <ListButton>list-button and <RefreshButton>refresh-button components.
headerButtonProps
You can use the headerButtonProps property to customize the wrapper element of the buttons at the header:
footerButtons
By default, the <Edit/> component has a <SaveButton> and a <DeleteButton> at the footer.
You can customize the buttons at the footer by using the footerButtons property. It accepts React.ReactNode or a render function ({ defaultButtons, saveButtonProps, deleteButtonProps }) => React.ReactNode which you can use to keep the existing buttons and add your own.
If canDelete is false, the <DeleteButton> will not render and deleteButtonProps will be undefined.
Or, instead of using the defaultButtons, you can create your own buttons. If you want, you can use saveButtonProps and deleteButtonProps to utilize the default values of the <SaveButton> and <DeleteButton> components.
footerButtonProps
You can customize the wrapper element of the buttons at the footer by using the footerButtonProps property.
autoSaveProps
You can use the auto save feature of the <Edit/> component by using the autoSaveProps property.
TIP
The query object from the useForm hook contains the query result from the data provider. You can use it to access the data returned from the API.
const { query } = useForm();
const record = query?.data?.data;
The data.data structure shown above is the default for the @refinedev/simple-rest data provider. This structure may be different for other data providers.
API Reference
Properties
| Property | Type | Description | Default |
|---|---|---|---|
resource | | Resource name for API data interactions | Reads |
title | | Title of the edit view | Edit {resource.name} |
wrapperProps | | Props for the wrapper component of the view | |
headerProps | | Props for the header component | |
contentProps | | Props for the content wrapper component | |
breadcrumb | | Breadcrumb to be displayed in the header |
|
goBack | | Back button element at the top left of the page | |
headerButtons | | Header action buttons to be displayed in the header | If |
headerButtonProps | Additional props to be passed to the wrapper of the header buttons | ||
footerButtons | | Footer action buttons to be displayed in the footer | If |
footerButtonProps | Additional props to be passed to the wrapper of the footer buttons | ||
dataProviderName | | To specify a data provider other than default use this property | |
isLoading | | Loading state of the component |
|
canDelete | | Adds a | If the resource has |
saveButtonProps | | Additional props for the | |
deleteButtonProps | | Adds properties for | |
mutationMode | |
| |
recordItemId | The record id for | ||
autoSaveProps | | Show <AutoSaveIndicator /> component on header buttons |
External Props
It also accepts all props of Ant Design Form.
Type Parameters
| Property | Extends | Default | Description |
|---|---|---|---|
| TQueryFnData | unknown | unknown | Result data returned by the query function. Extends unknown |
| TError | unknown | unknown | Custom error object that extends unknown |
| TVariables | object | object | Values for params. default object |
| TData | unknown | unknown | Result data returned by the select function. Extends unknown |
| TResponse | unknown | unknown | Result data returned by the mutation function. Extends unknown |
Return values
| Property | Description |
|---|---|
query | If the query prop is given, it will be returned. Otherwise, it will return undefined. |
mutation | Mutation result from react-query. Check here → |
saveButtonProps | Props for a save button. |
cancelButtonProps | Props for a cancel button. |
deleteButtonProps | Props for a delete button. |
formProps | Props for the <Form> component. |
formLoading | Loading state of form. |
setId | id setter. |
id | Record id for edit action. The record to edit. |
defaultValues | Default form values. |
formValues | Form values. |
submit | Submit method, the parameter is the values to update a record. |
reset | Reset method, reset the form values to initial values. |
redirect | Redirect function, will be called after form is submitted successfully. |
goBack | Go back function, will be called when the cancel button is clicked. |
query | Query result from react-query. Check here → |