microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Easy access to ODataNextLink
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Use case: We want to iterate pages on the client (via a call to the server that has app permissions), pass an opaque token from the server to the client that allows us to refer back to the ODataNextLink, and on paging pull out the ODataNextLink on the server and get the next page.
I know of the iteration workaround in https://github.com/microsoftgraph/dotnet-aad-query-sample/blob/0e2830c1a03eb24669d3ca4463698d55b8405133/GraphDataService/IAsyncEnumerableGraphExtensions.cs#LL33C63-L33C76 - that is nasty.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue’s paging use case and the linked IAsyncEnumerableGraphExtensions.cs workaround. Determine how the SDK could expose an opaque reference to ODataNextLink across client and server calls, then verify that paging can retrieve the next link without the workaround.
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