microsoftgraph / microsoftgraph/msgraph-sdk-dotnet-core

DeltaResponseHandler: add depth control

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Request: enhancement Status: Needs investigation
Dominant language
C#
Stars
164
Forks
65
Avg merge
38m
Merged PRs (30d)
1

Description

Internal customer request.

I would really like an option for controlling the "depth" for which the DeltaResponseHandler goes to add complex objects to the changelist.
For example in members@delta, Each membership added to a group shows up as 2 changes in the changelist. We process up to 500 memberships at a time, which means the changelist can be size 1000 even though we only care about the fact that memberships are added, and rely on DQ to include only the relevant ones. In this case, i'd want changelist to only include ["members@delta"] and that's it .
Something like new DeltaResponseHandler(depth:1) to only include the top level object would be great. Alternatively, only including the top level object for a complex object is fine with us too.
Reference
https://github.com/microsoftgraph/msgraph-sdk-dotnet-core/pull/58

AB#7173

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating DeltaResponseHandler and reviewing the linked pull request #58 to understand how nested changes are added to the changelist. Reproduce the members@delta example and define whether depth:1 or top-level-only behavior is the intended completion criteria; verify that the resulting changelist contains only members@delta.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.