React Data GridReact Hooks
react logo

This page explains best practices for using React Hooks with AG Grid.

Row Data

When setting Row Data, we recommend using useState or useMemo.

const App = () => {
    const [rowData, setRowData] = useState([
        {make: "Toyota", model: "Celica", price: 35000},
        {make: "Ford", model: "Mondeo", price: 32000},
        {make: "Porsche", model: "Boxster", price: 72000}

    return <AgGridReact rowData={rowData} />;

If you do NOT use useState or useMemo, then the grid will be provided with a new set of row data each time the parent component is rendered. This will result in unexpected behaviour in the grid, such as row selection resetting.

For applications that set data into the grid (as opposed to showing data statically), it makes sense to favour useState over useMemo as loading data usually aligns with changing state in your application.

All examples in the documentation use useState for Row Data.

Immutable Data

If you are going to be updating Row Data then it is strongly recommended to provide the getRowId callback that returns a unique id for each row. The grid is then able to identify Rows between new lists of Row Data. For example, if Rows are selected, and new Row Data is provided such that some Rows are removed, the grid is able to maintain the selection across rows that exist in both the old and new lists of Row Data.

See Updating Row Data for more information and other benefits of providing the getRowId callback.

Column Definitions

When setting Column Definitions, we recommend using useState or useMemo.

const App = () => {
    const [columnDefs, setColumnDefs] = useState([
        {field: 'make'},
        {field: 'model'},

    return <AgGridReact columnDefs={columnDefs} />;

If you do NOT use useState or useMemo, then the grid will be provided with a new set of Column Definitions every time the parent component is rendered. This will result in unexpected behaviour in the grid, such as the column state (column order, width etc...) getting reset.

If your application changes Column Definitions use useState, otherwise use useMemo.

const App = () => {
    // do NOT do this, will result in extra Grid processing
    const columnDefs = [
        {field: 'make'},
        {field: 'model'},

    return <AgGridReact columnDefs={columnDefs} />;

Object Properties vs Simple Properties

For all other properties that are Objects, e.g. sideBar and statusBar, we also recommend useState or useMemo. If you do not use these hooks, then you risk resetting the grid's state each time a render occurs. For example the Side Bar will get initialised with new configuration from sideBar property if a new instance of this property is created on each render.

const App = () => {

    // GOOD - only one instance created
    const sideBar = useMemo( ()=> {
        toolPanels: ['filters','columns']
    }, []);

    // BAD - each render could re-create the Status Bar in the grid
    const statusBar = {
        statusPanels: [ 
            { statusPanel: 'agTotalAndFilteredRowCountComponent' }

    return (
        <AgGridReact sideBar={sideBar} statusBar={statusBar} />

Properties of simple types (string, boolean and number) do not need to use hooks to prevent unnecessary grid state changes. This is because React uses JavaScript comparisons to determine if properties have changed, and JavaScript compares by value (not object references) for simple types.

const App = () => {

    const rowBuffer = 0;
    const rowSelection = 'multiple';

    return (
            // variables assigned, no hooks, properties
            // only set once

            // inline also works well, properties only set once


For callbacks (both Event Listeners and Grid Options that are functions), you can use useCallback() if you wish, or you can also just set the callback into the grid.

Not using useCallback() has no adverse effect on the grid, as changing such does not have any impact on the grid state (unlike Row Data and Column Definitions, which when changed, have immediate impact on the grid). Changing a callback means the new callback will be used next time it is needed.

If you do use useCallback(), make sure you set correct dependencies in order to avoid stale closures. We get many support issues due to application bugs resulting from stale closures.

const App = () => {
    const [clickedCount, setClickedCount] = useState(0);

    // good callback, no hook, no stale data
    const onCellClicked = () => setClickedRow(clickedCount++);

    // bad callback - stale data, dependency missing,
    // will ALWAYS print 0
    const onCellValueChanged = useCallback( ()=> {
        console.log(`number of clicks is ${clickedCount}`);
    }, []);

    // good callback, no stale data
    const onFilterOpened = useCallback( ()=> {
        console.log(`number of clicks is ${clickedCount}`);
    }, [clickedRow]);

    return <AgGridReact 


Custom Components can be referenced by Name or Direct Reference. This is explained in detail on the page Registering Components. However, it made sense to make reference to it here, as it's to do with integrating with the wider React Rendering Engine.

We recommend referencing components directly, unless you have a reason to reference by name. Reasons to reference by name would include a) wanting to make Column Definitions pure JSON or b) wanting to override default components (such as the default Header Component) provided by the grid.

We prefer Direct Reference as it results in nice looking Column Definitions.

We also recommend the use of memo around Components, to avoid wasted component renders on your Component.

Almost all of our examples, where Custom Components are used, are referenced directly. However the examples do not use memo to avoid clutter in the example.

const MyCellRenderer = p => <span>{p.value}</span>;

const App = () => {
    const [columnDefs] = useState([

        // reference the Cell Renderer above
        { field: 'make', cellRenderer: MyCellRenderer },
        // or put inline
        { field: 'model', cellRenderer: p => <span>{p.value}</span> },

        // optionally for best performance, memo() the renderer, so render
        // cycles don't occur unnecessarily
        { field: 'price', cellRenderer: memo(MyCellRenderer) }

    return <AgGridReact columnDefs={columnDefs} />;