--- canonical_url: https://refine.dev/blog/migrating-a-react-admin-application-to-refine/ title: Migrating a React-Admin Application to refine 💖 published: true description: tags: react, reactadmin, showdev, javascript cover_image: https://images.unsplash.com/photo-1577212363774-819fae14aeb2?ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&ixlib=rb-1.2.1&auto=format&fit=crop&w=2748&q=80 --- [refine][refine] is an extremely customizable [Ant Design][Ant Design] based [React][React] framework for data-intensive applications and it handles most of the CRUD functionality that can be a requirement in many applications, without much effort. Providing the rest of the desired functionality (outside CRUD) is up to you, like in any **React** application. [React-Admin][React-Admin] is an amazing B2B application framework based on [Material Design][Material Design], using [Material UI][MUI]. It provides ready-to-fetch-data components, so you just compose them together to create an application. **refine** is different in the way it makes you compose your application. refine directly provides **Ant Design** components and some hooks to work with those components. Hooks give you the required props for those Ant Design components. It is, also, one step forward towards the dream of **making it headless**. To learn more about refine, see: Recently, our team decided to migrate a B2B admin panel of one of our customers from React-Admin to refine to battle test our new framework and improve our productivity. My mission was to migrate it and it took one and a half days for me to rewrite the panel in refine. | ![resources menu after migration to refine](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bfolbjj75vru89afyiml.png) | |:--:| | *Our panel has 7 resources (all listable), which 4 of them must have create and edit pages, 6 of them must be exportable to `.csv` files and some of those resources have images, all images must be uploaded in `base64` format.* | This is how it looks before the migration (React-Admin): ![Admin panel in React-Admin](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/icri17tc2vf1cvngco7p.png) And this is how it looks like after the migration (refine): ![Admin panel in refine](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5amwrb2ciadtn5vi8pd4.png) Both of these images show a list page of a resource (campaign). ##Migrating Listing Pages List pages have one/more tables inside them. Ideally, all table state should be managed by the framework in use. refine is very flexible with tables. You can put them anywhere, configure it as much as you want with [useTable][useTable]. See the [fineFoods example][fineFoods example] and [it's code][fineFoods categories list]. Here is an example list page from React-Admin that shows you the list of `id`, `name`, `isActive`, `startDate`, `endDate` from the API endpoint for `campaigns` resource. ```tsx import React from "react"; import { List as ReactAdminList, Datagrid, TextField, BooleanField, EditButton } from "react-admin"; import LocalizeDateField from '../../fields/LocalizeDateField'; const List = (props) => ( ); export default List; ``` And looks like this: ![Admin panel in React-Admin](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/icri17tc2vf1cvngco7p.png) Here's the code that renders this same list in refine: ```tsx import React from "react"; import { List, Table, Space, Button, BooleanField, DateField, CreateButton, EditButton, ExportButton, Icons, useTable, getDefaultSortOrder, useExport, useDeleteMany, IResourceComponentsProps, } from "@pankod/refine"; import { ICampaign } from "interfaces"; export const CampaignsList: React.FC = () => { const { tableProps, sorter } = useTable({ initialSorter: [ { field: "id", order: "asc", }, ], }); const { isLoading: isExportLoading, triggerExport } = useExport(); const [selectedRowKeys, setSelectedRowKeys] = React.useState( [], ); const handleSelectChange = (selectedRowKeys: React.Key[]) => { setSelectedRowKeys(selectedRowKeys); }; const rowSelection = { selectedRowKeys, onChange: handleSelectChange, }; const { mutate, isLoading } = useDeleteMany(); const deleteSelectedItems = () => { mutate( { resource: "campaigns", ids: selectedRowKeys.map(String), mutationMode: "undoable", }, { onSuccess: () => { setSelectedRowKeys([]); }, }, ); }; const hasSelected = selectedRowKeys.length > 0; return ( deleteSelectedItems()} loading={isLoading} icon={ } > Delete ), extra: ( ), }}> } sorter defaultSortOrder={getDefaultSortOrder("isActive", sorter)} /> ( )} sorter defaultSortOrder={getDefaultSortOrder("startDate", sorter)} /> ( )} sorter defaultSortOrder={getDefaultSortOrder("endDate", sorter)} /> fixed="right" title="Actions" dataIndex="actions" render={(_, { id }) => ( )} />

); }; ``` It is long. Because we had to handle selection and bulk delete button manually. That's because refine is decoupled from Ant Design components' code, too. But the advantage here is that you use Ant Design. You can use the Ant Design's Table as however you like, and then connect its data with refine. The point is customizability. And it looks like this: ![Admin panel in refine](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5amwrb2ciadtn5vi8pd4.png) In refine, we use Ant Design's [Table][Ant Design Table] components. ##Migrating Create/Edit Pages A resource creation page's code looked like this in React-Admin: ```tsx import React from "react"; import { required, Create as ReactAdminCreate, SimpleForm, BooleanInput, TextInput, DateTimeInput } from "react-admin"; const Create = (props: any) => ( ); export default Create; ``` And it looks like this: ![React-Admin create page example](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3qouymvawrlpyhgb051a.png) For refine, code of our campaign create page looks like: ```tsx import { Create, DatePicker, Form, Input, IResourceComponentsProps, Switch, useForm, } from "@pankod/refine"; import dayjs from "dayjs"; export const CampaignsCreate: React.FC = () => { const { formProps, saveButtonProps } = useForm(); return ( ); }; ``` In both refine and React-Admin, by default, there aren't much differences between new resource page's code and resource edit page's code. Also note that for both refine and React-Admin, this is all customizable. These code examples and screenshots mean little or no extra customization in resource list/create/edit pages. Advantage of refine is that you use Ant Design directly. Let's assume you have your own way around your Ant Design application. refine doesn't interfere. Instead, it provides you the necessary data for your Ant Design application. This way, refine gives you all the freedom to customize all the components as you wish. Happy hacking with refine 🪄 {% github pankod/refine %} [refine]: https://refine.dev/ [React-Admin]: https://marmelab.com/react-admin/ [Ant Design]: https://ant.design/ [fineFoods example]: https://example.refine.dev/categories?current=1&pageSize=10&sort[]=title&order[]=asc [fineFoods categories list]: https://github.com/pankod/refine/blob/master/examples/fineFoods/src/pages/categories/list.tsx [useTable]: https://refine.dev/docs/api-references/hooks/table/useTable/ [Material Design]: https://material.io/ [MUI]: https://mui.com/ [React]: https://reactjs.org/ [Ant Design Github]: https://github.com/ant-design/ant-design [Ant Design Table]: https://ant.design/components/table/

umutozdemir97

Migrating a React-Admin Application to refine 💖

Join Our Newsletter. No Spam, Only the good stuff.