MudDataGrid form editing currently invokes CommittedItemChanges before the edited values are copied back to the bound row item. This makes object-level change detection difficult when consumers need to evaluate state after the actual model mutation.

• API addition

  • Added CommittedItemChanged to MudDataGrid<T>:
    • EventCallback<T> CommittedItemChanged { get; set; }
  • Intended for post-commit reactions on the final updated item.

• Commit flow update

  • Form mode: CommittedItemChanged is invoked after values are copied from the edit clone to the source item.
  • Cell mode: callback is invoked after CommittedItemChanges completes (item is already edited in-place in cell mode).
  • Existing CommittedItemChanges contract and KeepOpen behavior remain unchanged.

• Unit coverage

  • Added focused DataGrid test component + test to verify ordering:
    • CommittedItemChanges sees edited copy while source item is still unchanged.
    • CommittedItemChanged sees the source item after mutation.

• Docs

  • Updated DataGrid editing docs to clarify CommittedItemChanged as the post-apply hook.

Example

<MudDataGrid T="OrderLine"
             Items="@Lines"
             EditMode="DataGridEditMode.Form"
             ReadOnly="false"
             CommittedItemChanges="OnCommittedItemChanges"
             CommittedItemChanged="OnCommittedItemChanged" />

private Task<DataGridEditFormAction> OnCommittedItemChanges(OrderLine editedCopy)
{
    // pre-apply hook (clone in form mode)
    return Task.FromResult(DataGridEditFormAction.Close);
}

private Task OnCommittedItemChanged(OrderLine updatedItem)
{
    // post-apply hook (bound item is now updated)
    RecomputeDirtyState();
    return Task.CompletedTask;
}

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.