title allows the addition of titles inside the <Edit> component. if you don't pass title props it uses the "Edit" prefix and singular resource name by default. For example, for the "posts" resource, it would be "Edit post".
localhost:3000/posts/edit/123
import{Edit}from"@refinedev/chakra-ui"; import{Heading}from"@chakra-ui/react"; constPostEdit:React.FC=()=>{ return( <Edittitle={<Headingsize="lg">Custom Title</Heading>}> <p>Rest of your page here</p> </Edit> ); };
canDelete allows us to add the delete button inside the <Edit> component that executes the useDelete method provided by the dataProvider when clicked on.
If the resource has the canDelete property, refine adds the delete button by default. If you want to customize this button, you can use the deleteButtonProps property like the code below.
<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.
localhost:3000/custom/23
import{Edit}from"@refinedev/chakra-ui"; constCustomPage:React.FC=()=>{ return( <Editresource="categories"> <p>Rest of your page here</p> </Edit> ); };
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.
The <Edit> component reads the id information from the route by default. recordItemId is used when it cannot read from the URL(when used on a custom page, modal or drawer).
If not specified, refine will use the default data provider. If you have multiple data providers and want to use a different one, you can use the dataProviderName property.
To customize the back button or to disable it, you can use the goBack property. You can pass false or null to hide the back button.
localhost:3000/posts/edit/123
import{Edit}from"@refinedev/chakra-ui"; import{IconMoodSmile}from"@tabler/icons"; constPostEdit:React.FC=()=>{ return( <EditgoBack={<IconMoodSmile/>}> <p>Rest of your page here 2</p> </Edit> ); };
To customize or disable the breadcrumb, you can use the breadcrumb property. By default it uses the Breadcrumb component from @refinedev/chakra-ui package.
TIP
This feature can be managed globally via the <Refine> component's options
localhost:3000/posts/edit/123
import{Edit,Breadcrumb}from"@refinedev/chakra-ui"; import{Box}from"@chakra-ui/react"; constPostEdit:React.FC=()=>{ return( <Edit breadcrumb={ <BoxborderColor="blue"borderStyle="dashed"borderWidth="2px"> <Breadcrumb/> </Box> } > <p>Rest of your page here</p> </Edit> ); };
If you want to customize the wrapper of the <Edit/> component, you can use the wrapperProps property. For @refinedev/chakra-ui wrapper element is <Card>s and wrapperProps can get every attribute that <Card> can get.
localhost:3000/posts/edit/123
import{Edit}from"@refinedev/chakra-ui"; constPostEdit:React.FC=()=>{ return( <Edit wrapperProps={{ borderColor:"blue", borderStyle:"dashed", borderWidth:"2px", p:"2", }} > <p>Rest of your page here</p> </Edit> ); };
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.
CAUTION
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> and <RefreshButton> components.
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.
CAUTION
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.