Ronald K

LGTM

Hi @mblaschke , Thanks for reaching out, The suggestions presented are certainly interesting and worth exploring but the overall architecture of the SDK is defined by [design guidelines](https://github.com/microsoftgraph/msgraph-sdk-design/blob/master/tasks/PageIteratorTask.md). Another reason...

For this issue, I have come across this algorithm, a [bounded search](http://janmatuschek.de/LatitudeLongitudeBoundingCoordinates) that will help in looking up the locations via an index in the database. This is a combination...

Hi @kfcampbell are you still running into this issue with kiota v1.14.*?

The proposed change should simplify creating an iterator using the function ```go i, err := client.NewPageIterator(result) i.Iterate(context.Background(), func(pageItem interface{}) bool { return true }) ```

@baywet Yes we can, I considered that we might have breaking change but it does look worthwhile. This is definitely achievable ```go i, err := client.NewPageIterator[Groupable](result) i.Iterate(context.Background(), func(pageItem Groupable) bool...

An update on the progress of this issue. 1. The page iterator now take a generic type argument that enforces the type case in the iterator consumer function. 2. As...

This issue was resolved by https://github.com/microsoftgraph/msgraph-sdk-go-core/pull/177

Hi @galoslev Thanks for using the Go SDK and for reaching out. Looking at the v1 service metadata, this search parameter has been referenced with the dollar sign. I've created...

Hi @erictg, The current issue is not a result of a memory leak but is because of the size of the SDK. While we are working continuously on improving the...