[data grid] useGridApiRef returns RefObject, but DataGrid apiRef prop only accepts MutableRefObject

[ArmandRedgate]

Steps to reproduce

1. Add the following code to a project running @mui/x-data-grid-pro v7.23.6 and TypeScript:

const apiRef = useGridApiRef();

<DataGridPro
  apiRef={apiRef}
  />

Current behavior

Currently, we get an error of the style

Type RefObject<GridApiPro> is not assignable to type MutableRefObject<GridApiPro>

when trying to pass an apiRef from useGridApiRef() to the DataGrid component.

This issue is likely related to #16135, but more specifically causes us to not be able to use the api at all without an ugly cast like

const apiRef = useGridApiRef() as MutableRefObject<GridApiPro>;

Or am I missing something? I couldn't find any documentation on how to register the apiRef if not like this.

Expected behavior

useGridApiRef() returning a MutableRef

Context

Our support key is 65425.

We use the apiRef for all sorts of stuff, including exportState(), setRowChildrenExpansion and others.

Your environment

npx @mui/envinfo

  System:
    OS: Windows 11 10.0.26100
  Binaries:
    Node: 22.6.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (131.0.2903.146)
  npmPackages:
    @emotion/react:  11.10.6
    @emotion/styled:  11.10.6
    @mui/core-downloads-tracker:  6.4.0
    @mui/icons-material: 6.4.0 => 6.4.0
    @mui/material: 6.4.0 => 6.4.0
    @mui/private-theming:  6.4.0
    @mui/styled-engine:  6.4.0
    @mui/system:  6.4.0
    @mui/types:  7.2.21
    @mui/utils:  6.4.0
    @mui/x-data-grid:  7.23.6
    @mui/x-data-grid-pro: 7.23.6 => 7.23.6
    @mui/x-internals:  7.23.6
    @mui/x-license:  7.23.6
    @types/react: 18.3.18 => 18.3.18
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1
    typescript: 5.7.3 => 5.7.3

Search keywords: MutableRefObject apiRef GridApi

[michelengelen]

duplicate of #16000

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@ArmandRedgate How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.