useSelect

useSelect hook allows you to manage Mantine's <Select> component when records in a resource needs to be used as select options.

This hook uses the useList hook for fetching data. Refer to useList hook documentation for details. →

Usage​

Here is a basic example of how to use useSelect hook.

import { useSelect } from "@refinedev/mantine";
import { Select } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
  });

  return (
    <Select
      label="Category"
      placeholder="Select a category"
      withinPortal
      {...selectProps}
    />
  );
};

Realtime Updates​

LiveProvider is required for this prop to work.

When useSelect hook is mounted, it passes some parameters (channel, resource etc.) to the subscribe method from the liveProvider. It is useful when you want to subscribe to the live updates.

Properties​

resource

required

​

It will be passed to the getList method from the dataProvider as parameter via the useList hook. The parameter is usually used as an API endpoint path. It all depends on how to handle the resource in the getList method. See the creating a data provider section for an example of how resources are handled.

useSelect({
  resource: "categories",
});

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 identifier section of the <Refine/> component documentation →

optionLabel and optionValue​

Allows you to change the value and label of your options. Default values are optionLabel = "title" and optionValue = "id"

useSelect<ICategory>({
    resource: "products",
    optionLabel: "name"
    optionValue: "productId"
});

These properties also support nested properties via Object path syntax.

const { options } = useSelect({
  resource: "categories",
  optionLabel: "nested.title",
  optionValue: "nested.id",
});

sorters​

It allows to show the options in the desired order. sorters will be passed to the getList method from the dataProvider as parameter via the useList hook. It is used to send sort query parameters to the API.

For more information, refer to the CrudSorting interface documentation →

useSelect({
  sorters: [
    {
      field: "title",
      order: "asc",
    },
  ],
});

import { useSelect } from "@refinedev/mantine";
import { Select, Button } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const [order, setOrder] = React.useState<"asc" | "desc">("asc");

  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
    sorters: [
      {
        field: "title",
        order,
      },
    ],
  });

  return (
    <>
      <Button onClick={() => setOrder(order === "asc" ? "desc" : "asc")}>
        Toggle Order
      </Button>
      <Select
        label="Category"
        placeholder="Select a category"
        withinPortal
        {...selectProps}
      />
    </>
  );
};

filters​

It is used to show options by filtering them. filters will be passed to the getList method from the dataProvider as parameter via the useList hook. It is used to send filter query parameters to the API.

For more information, refer to the CrudFilters interface documentation →

useSelect({
  filter: [
    {
      field: "isActive",
      operator: "eq",
      value: true,
    },
  ],
});

defaultValue​

defaultValue allows you to make options selected by default and adds extra options to <select> component. In some cases, like if there are too many entries for the <select> and pagination is required, defaultValue may not be present in the current visible options and this can break the <select> component. To avoid such cases, A separate useMany query is sent to the backend with the defaultValue and appended to the options of <select>, ensuring the default values exist in the current options array. Since it uses useMany to query the necessary data, the defaultValue can be a single value or an array of values like the following:

useSelect({
  defaultValue: 1, // or [1, 2]
});

For more information, refer to the useMany documentation →

debounce​

debounce allows us to debounce the onSearch function.

useSelect({
  debounce: 500,
});

queryOptions​

queryOptions is used to pass additional options to the useQuery hook. It is useful when you want to pass additional options to the useQuery hook.

For more information, refer to the useQuery documentation →

useSelect({
  queryOptions: {
    retry: 3,
  },
});

pagination​

pagination will be passed to the getList method from the dataProvider as parameter. It is used to send pagination query parameters to the API.

current​

You can pass the current page number to the pagination property.

useSelect({
  pagination: {
    current: 2,
  },
});

pageSize​

You can pass the pageSize to the pagination property.

useSelect({
  pagination: {
    pageSize: 20,
  },
});

mode​

It can be "off", "client" or "server". It is used to determine whether to use server-side pagination or not.

useSelect({
  pagination: {
    mode: "off",
  },
});

defaultValueQueryOptions​

When the defaultValue property is given, the useMany data hook is called for the selected records. With this property, you can change the options of this query. If not given, the values given in queryOptions will be used.

const { options } = useSelect({
  defaultValueQueryOptions: {
    onSuccess: (data) => {
      console.log("triggers when on query return on success");
    },
  },
});

onSearch​

onSearch allows us to AutoComplete the options.

import { useSelect } from "@refinedev/mantine";
import { Select } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
    onSearch: (value) => [
      {
        field: "title",
        operator: "contains",
        value,
      },
    ],
  });

  return (
    <Select
      label="Category"
      placeholder="Select a category"
      withinPortal
      {...selectProps}
    />
  );
};

If onSearch is used, it will override the existing filters.

For more information, refer to the CrudFilters interface documentation →

Client-side filtering​

Sometimes, you may want to filter the options on the client-side. You can do this by passing the onSearch function as undefined. This will disable the server-side filtering and will filter the options on the client-side. Set the searchValue and onSearchChange properties to enable the search input.

const { selectProps } = useSelect({
  resource: "categories",
});

const [searchValue, onSearchChange] = useState("");

<Select
  {...selectProps}
  onSearch={undefined}
  onSearchChange={onSearchChange}
  searchValue={searchValue}
/>;

meta​

meta is a special property that can be used to pass additional information to data provider methods for the following purposes:

• Customizing the data provider methods for specific use cases.
• Generating GraphQL queries using plain JavaScript Objects (JSON).

For more information, refer to the meta section of the General Concepts documentation →

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

useSelect({
  meta: {
    headers: { "x-meta-data": "true" },
  },
});

const myDataProvider = {
  //...
  getList: async ({
    resource,
    pagination,
    sorters,
    filters,
    meta,
  }) => {
    const headers = meta?.headers ?? {};
    const url = `${apiUrl}/${resource}`;
    //...
    //...
    const { data, headers } = await httpClient.get(`${url}`, { headers });
    return {
      data,
    };
  },
  //...
};

dataProviderName​

If there is more than one dataProvider, you can specify which one to use by passing the dataProviderName prop. It is useful when you have a different data provider for different resources.

useSelect({
  dataProviderName: "second-data-provider",
});

successNotification​

NotificationProvider is required for this prop to work.

After data is fetched successfully, useSelect can call open function from NotificationProvider to show a success notification. With this prop, you can customize the success notification.

useSelect({
  successNotification: (data, values, resource) => {
    return {
      message: `${data.title} Successfully fetched.`,
      description: "Success with no errors",
      type: "success",
    };
  },
});

errorNotification​

NotificationProvider is required for this prop to work.

After data fetching is failed, useSelect will call open function from NotificationProvider to show a error notification. With this prop, you can customize the error notification.

useSelect({
  errorNotification: (data, values, resource) => {
    return {
      message: `Something went wrong when getting ${data.id}`,
      description: "Error",
      type: "error",
    };
  },
});

liveMode​

LiveProvider is required for this prop to work.

Determines whether to update data automatically ("auto") or not ("manual") if a related live event is received. It can be used to update and show data in Realtime throughout your app.

useSelect({
  liveMode: "auto",
});

onLiveEvent​

LiveProvider is required for this prop to work.

The callback function that is executed when new events from a subscription are arrived.

useSelect({
  onLiveEvent: (event) => {
    console.log(event);
  },
});

liveParams​

LiveProvider is required for this prop to work.

Params to pass to liveProvider's subscribe method.

overtimeOptions​

If you want loading overtime for the request, you can pass the overtimeOptions prop to the this hook. It is useful when you want to show a loading indicator when the request takes too long. interval is the time interval in milliseconds while onInterval is the function that will be called on each interval.

Return overtime object from this hook. elapsedTime is the elapsed time in milliseconds. It becomes undefined when the request is completed.

const { overtime } = useSelect({
  //...
  overtimeOptions: {
    interval: 1000,
    onInterval(elapsedInterval) {
      console.log(elapsedInterval);
    },
  },
});

console.log(overtime.elapsedTime); // undefined, 1000, 2000, 3000 4000, ...

// You can use it like this:
{
  elapsedTime >= 4000 && <div>this takes a bit longer than expected</div>;
}

sort

deprecated

​

Use sorters instead.

hasPagination

deprecated

​

Use pagination.mode instead.

FAQ​

How to add search to options (Autocomplete)?​

onSearch is a function that is used to set the search value. It is useful when you want to search for a specific value. A simple example of this is shown below.

import { useSelect } from "@refinedev/mantine";
import { Select } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
    onSearch: (value) => [
      {
        field: "title",
        operator: "contains",
        value,
      },
    ],
  });

  return (
    <Select
      label="Category"
      placeholder="Select a category"
      withinPortal
      {...selectProps}
    />
  );
};

How to ensure defaultValue is included in the options?​

In some cases we only have id, it may be necessary to show it selected in the selection box. This hook sends the request via useMany, gets the data and mark as selected.

import { useSelect } from "@refinedev/mantine";
import { Select, Button } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
    defaultValue: 11,
  });

  return (
    <>
      <Select
        label="Category"
        placeholder="Select a category"
        withinPortal
        {...selectProps}
      />
    </>
  );
};

How to change the label and value properties in options?​

optionLabel and optionValue are used to change the value of your options. The default values are optionsLabel="title" and optionsValue="id".

To change to name and categoryId;

useSelect({
  optionLabel: "name",
  optionValue: "categoryId",
});

Can I create the options manually?​

Sometimes it may not be enough to create optionLabel and optionValue options. In this case we create options with queryResult.

const { queryResult } = useSelect();

const options = queryResult.data?.data.map((item) => ({
  label: item.title,
  value: item.id,
}));

return <Select options={options} />;

How do I use it with CRUD components and useForm?​

import { Create, useForm, useSelect } from "@refinedev/mantine";
import { Select } from "@mantine/core";

interface ICategory {
  id: number;
  title: string;
}

const ProductCreate: React.FC = () => {
  const { saveButtonProps, getInputProps, errors } = useForm({
    initialValues: {
      category: {
        id: "",
      },
    },
  });

  const { selectProps } = useSelect<ICategory>({
    resource: "categories",
  });

  return (
    <Create saveButtonProps={saveButtonProps}>
      <form>
        <Select
          mt={8}
          label="Category"
          placeholder="Select a category"
          {...getInputProps("category.id")}
          {...selectProps}
        />
      </form>
    </Create>
  );
};

API Reference​

Properties​

Type Parameters​

Return values​

SelectPropsType​

Property	Description	Type
data	Select data used to renderer items in dropdown	(string \| SelectItem)[]
searchable	Set to true to enable search	boolean
onSearchChange	Called each time search value changes	(query: string) => void
filterDataOnExactSearchMatch	Should data be filtered when search value exactly matches selected item	boolean

Example​

npm create refine-app@latest -- --example base-mantine