Nikitha Chettiar
Nikitha Chettiar
Investigate the following use cases: - [ ] using only model classes, create a long chain of nested objects which are interlooped. - [ ] using model interfaces, test use...
The current design of TypeScript maps a request body object to the model class at the time of request as follows: interface User { name: string } const user: User...
https://github.com/microsoft/kiota/pull/1559#discussion_r869229484
The Kiota Generation must also generate a `index.ts` barrel file which would do the following: - [ ] Export models - [ ] Export the request configuration parameter types/ classes...
Related to #1494. Use interfaces for config options instead of class
> Definitely, this would add a lot of value here. But, why are we using classes vs Interfaces? Interfaces would allow us to achieve this. There is probably a reason...
Document how to use RequestOptions to with `MiddlewareOptions`, `FetchOptions`
The failure is as follows - https://github.com/microsoftgraph/MSGraph-SDK-Code-Generator/pull/488/checks?check_run_id=2125318477 On retriggering, this check didn't report the same failure and passed successfully. [AB#8623](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/8623)
Example - `ERROR: 28964:1 max-line-length Exceeds maximum line length of 200` This error gets reported when linting with dtslint. The code should consider the line length during generation. [AB#7091](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/7091)
Today I am excited to announce the **preview** release of [Microsoft Graph JavaScript Client Library 4.0.0-RestPreview.1](https://www.npmjs.com/package/@microsoft/microsoft-graph-client/v/4.0.0-RestPreview.1) `npm i @microsoft/[email protected]` > **Note**: The `@microsoft/microsoft-graph-client/v/4.0.0-RestPreview.1` release is not ready for production use....