Ronald K

Hi @universam1, as of release 0.106.0 this issue should be resolved

I would agree with fail first rather than serializing it to a nil. Of concern, it will be almost impossible for developers to know if the enum value was not...

@baywet We should be able to support type inference by making the following changes to the Page Iterator and the sdk generator this would be the result ```go msgraphcore.NewPageIterator(pages, client.GetAdapter(),...

@baywet I do agree with the change for constructor behavior ```diff -func NewSitePage() *SitePage +func NewSitePage() SitePageable ``` This will not be source breaking, but it will help with automatic...

@baywet Here is some [sample code ](https://github.com/microsoftgraph/msgraph-sdk-go-core/compare/main...fix/improve-page-iterator-type)that works in a branch . Only change that was required for type hinting is the constructor is ```diff -func NewSitePage() *SitePage +func NewSitePage()...

In that case the only other way possible way I can think of is to generate a registry on the client that returns a map of `[package.objectName]factoryMethod` on the client...

Only concern with that is there is no compile time validation with the discriminator method.

Related to https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/1968

Hi @dcormier, Thanks for trying the MS Graph Go SDK. As of now , [v1.44.0](https://github.com/microsoftgraph/msgraph-sdk-go/releases/tag/v1.44.0) of graph go sdk, it [does not support](https://learn.microsoft.com/en-us/graph/api/user-post-messages?view=graph-rest-1.0&tabs=go#request-2) sending RFC 5322-formatted message. You should still...

@CmckeeverNova would you mind sharing the version of the sdk you are using and some of the missing fields. In the meantime you should be able to access the fields...