Library has moved?

Question

To Whom It May Concern:

I am trying to follow along with the example to be able to open messages from my email and place them into my app. I'm following the instructions on: https://learn.microsoft.com/en-gb/graph/sdks/paging?tabs=Go

However, this library, "graph "github.com/microsoftgraph/msgraph-sdk-go/models/microsoft/graph", no longer seems to be present in the msgraph-sdk-go directory. Where would these models be placed?

Answer 1

Hi @DannyAdams-2744 ,

Please note that Microsoft Graph GO SDK is currently in preview and which is subject to change. Use of this SDK in production is not supported. GitHub team makes changes to these SDKs. I have also verifed Microsoft Graph Go SDK repository in GitHub but I am also unable to find graph module "github.com/microsoftgraph/msgraph-sdk-go/models/microsoft/graph" located under "github.com/microsoftgraph/msgraph-sdk-go/models" directory.

However as documented here in these examples, you should be able to import this Microsoft Graph GO SDK graph module (github.com/microsoftgraph/msgraph-sdk-go/models/microsoft/graph) in your program / application.

If you are unable to import this Microsoft Graph GO SDK graph module then I would advise to raise an issue using the below links with Github SDKs support team to provide you the required support on this.

https://github.com/microsoftgraph/msgraph-sdk-go/issues
https://github.com/microsoftgraph/msgraph-sdk-go/discussions/categories/q-a

Hope this helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any further questions about this answer, please click "Comment".

Answer 2

Libraries move constantly as the msgraph-sdk-go is currently under development.
I apologize for my first message as it was unclear. In order to begin the query process, it's important to create the adapter and the client which are now located:
"github.com/microsoftgraph/msgraph-sdk-go"
See GraphServiceClient and GraphRequestAdapter

The discussion forum is the preferred way of conversing about misunderstandings. It is also important to check the Known Issues thread as some of the functionality is still under development.