[DataGrid] Fix cell editing of computed columns with data source

[ptuukkan]

I noticed that if there is a column which does not have a respective property in row data and using dataSource and cell editing, dataSource.editRow does not fire. This can happen with computed columns, for example.

This is due to the code checking if the row[field] has changed. In this case it would be always undefined and the updateStateToStopCellEditMode would return early without calling dataSource.editRow. useGridRowEditing uses isDeepEqual instead to check if something in the row has been changed. I thought it might be reasonable to use it in useGridCellEditing as well. Perhaps it wouldn't even be necessary to do that checking, but I will leave that decision to you.

Here is a sandbox inspired by the following demo: https://mui.com/x/react-data-grid/editing/#value-parser-and-value-setter
https://stackblitz.com/edit/tswwgcr5-5zr3q5b1?file=src%2FDemo.tsx

Editing the Computed column causes no updates to the grid nor it fires the dataSource.updateRow.

Here is the same sandbox with this PR's changes:
https://stackblitz.com/edit/uouznmzp?file=src%2FDemo.tsx

• I have followed (at least) the PR section of the contributing guide.

[github-actions]

Thanks for adding a type label to the PR! 👍

[mui-bot]

Deploy preview: https://deploy-preview-17684--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against ff42466

[MBilalShafi]

Thank you, @ptuukkan, for the PR. The change makes sense to me. It could indeed be possible to sync computed columns on the server. I added a test to make sure it keeps working as expected.

Perhaps it wouldn't even be necessary to do that checking

I would keep it to eliminate false positive runs of editRow, which would mean unnecessary API calls and cache resets.

@arminmeh I'd love another pair of eyes, though feel free to ignore the review request if you wish.