new method - FollowLocation/Next link

[baywet]

there are multiple scenarios on APIs that return a link to a resources:

• paging returns a link to the next page
• long running operations return a link to the status monitor resource
• creation might return a location with 201 (not followed by the redirect handler)

We currently already generate a constructor overload for a raw URL, but finding the constructor is hard for client users.

We could emit a method named "FollowLocation(uri)" next to the Get/Post method that people would call, with the next link they received from the initial call.

Pseudo code example

var firstPage = await client.Users.GetAsync();
var secondPage = await client.Users.FollowLocationAsync(firstPage.NexLink);

We'd need an extension to trigger the generation of that method, next steps @darrelmiller to spec out the extension

[isvargasmsft]

Another use case, I think, would be the reports API: https://learn.microsoft.com/en-us/graph/api/reportroot-getsharepointsiteusagedetail?view=graph-rest-1.0&tabs=http

[baywet]

@isvargasmsft I'm not sure how this is a good example for this issue since we're already projecting a code path and it the location header is returned with a 302. Our middleware should follow it already today. https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/e8d45240d46a84c12ccd683bac59c454ab02b017/src/Microsoft.Graph/Generated/Reports/GetSharePointSiteUsageDetailWithPeriod/GetSharePointSiteUsageDetailWithPeriodRequestBuilder.cs#L41

[darrelmiller]

We have decided to not do this work as there is currently insufficient information in the OpenAPI description to enable a good developer experience.

• Knowing the location URL in a 201 or 202 does not allow us to know the return type
• Paging can be addressed in other mechanism such as the page iterator, or future GetAll() implementions.