correct-apricot•3y ago

Route

create a nested menu or dropdown for your resources in Refine

8 Replies

Hi @tuanna_. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- To create a nested menu or dropdown for your resources in Refine, you can use the useMenu hook and the meta.parent property in your resources. Here's an example of how you can do this:

import { Refine } from "@refinedev/core";  
import routerProvider, { NavigateToResource } from "@refinedev/react-router-v6";  
import dataProvider from "@refinedev/simple-rest";  
import { BrowserRouter, Routes, Route, Outlet } from "react-router-dom";  

const API_URL = "<https://api.fake-rest.refine.dev";>  

const App: React.FC = () => {  
 return (  
 <BrowserRouter>  
 <Refine  
 routerProvider={routerProvider}  
 dataProvider={dataProvider(API_URL)}  
 resources={[  
 {  
 name: "CMS",  
 },  
 {  
 name: "posts",  
 list: "/CMS/posts",  
 meta: { parent: "CMS" },  
 },  
 {  
 name: "categories",  
 list: "/CMS/categories",  
 meta: { parent: "CMS" },  
 },  
 ]}  
 >  
 <Routes>  
 <Route  
 element={<Layout><Outlet /></Layout>}  
 >  
 <Route index element={<NavigateToResource />} />  
 <Route  
 path="/posts"  
 element={<div>dummy posts page</div>}  
 />  
 <Route  
 path="/categories"  
 element={<div>dummy categories page</div>}  
 />  
 </Route>  
 </Routes>  
 </Refine>  
 </BrowserRouter>  
 );  
};  

export default App;

import { Refine } from "@refinedev/core";  
import routerProvider, { NavigateToResource } from "@refinedev/react-router-v6";  
import dataProvider from "@refinedev/simple-rest";  
import { BrowserRouter, Routes, Route, Outlet } from "react-router-dom";  

const API_URL = "<https://api.fake-rest.refine.dev";>  

const App: React.FC = () => {  
 return (  
 <BrowserRouter>  
 <Refine  
 routerProvider={routerProvider}  
 dataProvider={dataProvider(API_URL)}  
 resources={[  
 {  
 name: "CMS",  
 },  
 {  
 name: "posts",  
 list: "/CMS/posts",  
 meta: { parent: "CMS" },  
 },  
 {  
 name: "categories",  
 list: "/CMS/categories",  
 meta: { parent: "CMS" },  
 },  
 ]}  
 >  
 <Routes>  
 <Route  
 element={<Layout><Outlet /></Layout>}  
 >  
 <Route index element={<NavigateToResource />} />  
 <Route  
 path="/posts"  
 element={<div>dummy posts page</div>}  
 />  
 <Route  
 path="/categories"  
 element={<div>dummy categories page</div>}  
 />  
 </Route>  
 </Routes>  
 </Refine>  
 </BrowserRouter>  
 );  
};  

export default App;

In this example, the posts and categories resources are nested under the CMS resource. The meta.parent property is used to specify the parent resource for each nested resource. For more information, you can refer to the Refine documentation on multi-level menus (https://refine.dev/docs/advanced-tutorials/multi-level-menu/) and the Refine documentation on the useMenu hook (https://refine.dev/docs/api-reference/core/hooks/ui/useMenu/). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•3y ago

<@353701348463738885> kapa.ai is still learning and improving, please let us know how it did by reacting below

correct-apricotOP•3y ago

@kapa.ai how to set icon to parent route

kapa.ai•3y ago

Let me check the knowledge base for you. One moment! :books: ---------------------- To set an icon to a parent route in Refine, you can use the meta.icon property in your resources. You can pass an icon element as a property for the icon in the menu. Here's an example of how you can do this:

import { Refine } from "@refinedev/core";  
import { CustomIcon } from "your-icon-path"; // replace with your actual icon component

const App: React.FC = () => {  
 return (  
 <Refine  
 resources={[  
 {  
 name: "parent",  
 meta: {  
 icon: <CustomIcon />  
 },  
 },  
 {  
 name: "child",  
 meta: {  
 parent: "parent",  
 },  
 },  
 ]}  
/>  
 );  
};  

export default App;

import { Refine } from "@refinedev/core";  
import { CustomIcon } from "your-icon-path"; // replace with your actual icon component

const App: React.FC = () => {  
 return (  
 <Refine  
 resources={[  
 {  
 name: "parent",  
 meta: {  
 icon: <CustomIcon />  
 },  
 },  
 {  
 name: "child",  
 meta: {  
 parent: "parent",  
 },  
 },  
 ]}  
/>  
 );  
};  

export default App;

In this example, the CustomIcon is set as the icon for the parent resource. The child resource is nested under the parent resource. For more information, you can refer to the Refine documentation on the <Refine> component (https://refine.dev/docs/api-reference/core/components/refine-config/). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•3y ago

<@353701348463738885> kapa.ai is still learning and improving, please let us know how it did by reacting below

correct-apricotOP•3y ago

@kapa.ai it not works, idk

kapa.ai•3y ago

Let me check the knowledge base for you. One moment! :books: ---------------------- I'm sorry to hear that you're having trouble. Based on the information provided in the extracts, I can't provide a specific solution to your problem. However, I can suggest some general troubleshooting steps: 1. Make sure you have the latest version of Refine installed. You can check your version by running npm list @pankod/refine in your terminal. If you don't have the latest version, you can update it by running npm update @pankod/refine. 2. Check your console for any error messages. These can provide clues about what's going wrong. 3. Make sure your icon component is correctly imported and can be rendered independently. 4. Ensure that the name property of your resources matches the actual names of your resources. If you're still having trouble, I recommend checking out the Refine documentation (https://refine.dev/docs) or reaching out to the Refine community for more specific help. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•3y ago

<@353701348463738885> kapa.ai is still learning and improving, please let us know how it did by reacting below

Route

Did you find this page helpful?