General Concepts

refine passes the resource to the dataProvider 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.

How does refine know what the resource value is?

1- The resource value is determined from the active route where the component or the hook is used.

Like below, if you are using the hook in the <PostList> component, the resource value defaults to "posts".

import { Refine } from "@pankod/refine-core";
import dataProvider from "@pankod/refine-simple-rest";
import routerProvider from "@pankod/refine-react-router-v6";

import { PostList } from "pages/posts/list.tsx";

const App: React.FC = () => {
  return (
    <Refine
      routerProvider={routerProvider}
      dataProvider={dataProvider("https://api.fake-rest.refine.dev")}
      resources={[
        {
          name: "posts",
          list: PostList,
        },
      ]}
    />
  );
};

export default App;

2- The resource value is determined from the resource prop of the hook.

You can override the default resource value hook by passing the resource prop to the hook like below:

import { useTable } from "@pankod/refine-core";

const PostList: React.FC = () => {
  const result = useTable({
    resource: "users",
  });

  return <div>...</div>;
};

How can I request an API with nested route?

Refer to how to use resource with nested routes documentation for more information. →

metaData is used following two purposes:

• To pass additional information to data provider methods.
• Generate GraphQL queries using plain JavaScript Objects (JSON).

How to use metaData to pass additional information to data provider methods?

useOne({
    resource: "posts",
    id: 1,
    metaData: {
        headers: { "x-meta-data": "true" },
    },
});

const myDataProvider = {
    ...
    getOne: async ({ resource, id, metaData }) => {
        const headers = metaData?.headers ?? {};
        const url = `${apiUrl}/${resource}/${id}`;

        const { data } = await httpClient.get(url, { headers });

        return {
            data,
        };
    },
    ...
};

In the above example, we pass the headers property in the metaData object to the getOne method. With similar logic, you can pass any properties to specifically handle the data provider methods.

Refer to the how to pass metaData to your existing dataProvider methods. →

Refer to the GraphQL guide to learn how to use metaData to create GraphQL queries. →