Improved Handling of Unchanged Objects in Graph API .NET SDK

I would like to propose an enhancement to the Graph API .NET SDK that enables better handling of unchanged objects during patch and post operations. Currently, even if there are no changes in the object being updated, the patch operation is still executed. This feature request aims to provide a mechanism for identifying if an object has updated values and to prevent unnecessary execution of patch and post operations when no changes are present.

Maybe there is already a technique that can be used to accomplish this goal.

Describe the solution you'd like
The suggested solution involves introducing two key features: the ability to identify if an object has updated values and the option to skip patch and post operations when no changes exist in the backing store. By implementing these features, developers can improve the efficiency and reduce unnecessary API calls in scenarios where object updates are conditional based on changes.

var userId = "putYourUserId";
var user = await graphClient.Users[userId].GetAsync();

// Check if the user object has any updated values
bool hasChanges = user.HasChanges();

if (hasChanges)
{
    // Implement the business logic to perform updates on the object

    // Perform the patch operation only if there are changes
    await graphClient.Users[user.Id].PatchAsync(user);
}
else
{
    // No changes, skip the patch operation
    Console.WriteLine("No changes found in the user object. Skipping patch operation.");
}

In the example above, the HasChanges() method is introduced to determine if the object contains any modified properties. This method compares the object's current state with the original values stored in the backing store to identify changes.

With this enhancement, developers gain more control over when to execute patch and post operations, preventing unnecessary API calls and improving performance in scenarios where updates are conditional.

Start by tracing the .NET SDK's backing-store behavior and the PATCH and POST operation paths; the issue names no files or tests. Clarify the intended HasChanges semantics and how unchanged objects should be detected, then define tests showing that changed objects are sent and unchanged objects skip unnecessary calls.