Michael Mainer

One solution to consider for test purposes: let's start copying-paste code as needed from service library.

When using the service library, we know the type expected in the collection of items returned in the response. This allows the developer to pass a delegate to process each...

Note to self that the generated API sets the ContentType to default octet-stream for HasStream. If a customer sets HeaderOption for ContentType in .Request(), we must use that value instead...

- [ ] Open issues on Java, JS, and PowerShell. cc:/ @peombwa @nikithauc @baywet

We already have this for the npm package (see https://github.com/microsoftgraph/msgraph-typescript-typings/blob/master/scripts/src/CalculateNewProductionVersion.ps1). It really is a matter of auto-incrementing for DefinatelyTyped. We may want to add that at generation, or post processing.

We published typings to npm before we published to DefinatelyTyped. DefinatelyTyped PR validation caught an error. We should use the same (or similar) validation on our PRs so we catch...

FieldValueSet is an opentype where the properties are user defined in SharePoint list items. They cannot be typed ahead of time. The only potentially typed property is ID as specified...

@Geoffrynagy and @BovineEnthusiast I was incorrect. @nikithauc we need to account for opentypes when we generate for TypeScript. ``

@krototype We'll need to update the generator to insert the odata.type and a comment to hint what the value should be. https://github.com/microsoftgraph/MSGraph-SDK-Code-Generator/blob/dev/Templates/TypeScript/src/entity_types.ts.tt#L71

Until this is address in the generator, you'll need to set this property on the FileAttachment object. We will need to address this for all types that descend from abstract...