[data grid] apiRef prop and the return type of useGridApiRef() does not match in Pro and Premium versions of the grid

[tsmithhisler]

Steps to reproduce

Steps:

1. Recreate this example using DataGridPro instead of DataGrid and v7.23.6 of mui-x https://mui.com/x/react-data-grid/api-object/#outside-the-data-grid
2. See Type 'RefObject<GridApiPro>' is not assignable to type 'MutableRefObject<GridApiPro>'. error

After upgrading to v7.23.6, it appears the DataGridPro props were not updated while the DataGrid props were. See the following: v7.23.5...v7.23.6#diff-18991c189d0e0b75b030b0889cfbee75905b8b4c19361d0a4b975a1a3ac26945L418

Current behavior

Typescript fails to compile when using useGridApiRef() with DataGridPro

Expected behavior

No response

Context

No response

Your environment

No response

Search keywords: data grid pro

[TrevorThomp]

Having the same issue as well:

Type 'RefObject<GridApiPremium>' is not assignable to type 'MutableRefObject<GridApiPremium>'. Types of property 'current' are incompatible. Type 'GridApiPremium | null' is not assignable to type 'GridApiPremium'. Type 'null' is not assignable to type 'GridApiPremium'.

[matzxrr]

Casting to any is the workaround for the moment.

apiRef={apiRef as any}

[arminmeh]

@tsmithhisler thanks for reporting this.
I will make a PR with the fix today.

In the meantime, you can use workaround from @matzxrr

[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

@tsmithhisler 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.