microsoft-graph-devx-api
microsoft-graph-devx-api copied to clipboard
microsoftgraph
Services API for Graph Explorer
This is to enable users to access the API resources from the closest server to them and therefore reduce latency. [AB#9013](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/9013)
**Is your feature request related to a problem? Please describe.** When calling `/permissions?requesturl=/users/&method=GET` to get permissions for `/users` endpoint, we get permissions that require special licenses such as Intune. ***Returned...
A pipeline which does: - generate snippets for the base branch - generate snippets for the feature branch - report the diff for PR. [AB#8096](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/8096)
See #288 for the issue description. See #427 for the C# counterpart of the fix. [AB#7807](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/7807)
The mail apis now have examples sending mails as mime payloads. Examples include - https://docs.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http#example-4-send-a-new-message-using-mime-format - https://docs.microsoft.com/en-us/graph/api/message-forward?view=graph-rest-1.0&tabs=http#example-2-forward-a-message-using-mime-content Support for the snippet generator for this needs to be added for the...
Source: https://docs.microsoft.com/en-us/graph/api/channel-post-messages?view=graph-rest-beta&tabs=csharp#request-1 Input: ```http POST https://graph.microsoft.com/beta/teams/57fb72d0-d811-46f4-8947-305e6072eaa5/channels/19:[email protected]/messages Content-type: application/json { "createdDateTime":"2019-02-04T19:58:15.511Z", "from":{ "user":{ "id":"id-value", "displayName":"Joh Doe", "userIdentityType":"aadUser" } }, "body":{ "contentType":"html", "content":"Hello World" } } ``` Erroneous output: ```C# GraphServiceClient graphClient...
**Describe the bug** Currently DevX API reads metadata and OpenAPI documents directly from `msgraph-metadata` GitHub repo, which makes it susceptible to issues like: https://github.com/microsoftgraph/msgraph-metadata/pull/172 **Expected behavior** Production sources should be...
- [x] Create milestones - [ ] Define process for creating releases - [ ] Define way of identifying what version of API is deployed? [AB#7021](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/7021)
In order to catch potential bugs in DevX API before they are deployed to production, we need to come up with a strategy to write [end-to-end tests](https://www.perfecto.io/blog/comprehensive-guide-end-end-e2e-testing?__cf_chl_f_tk=TdBESRiMCNRwo8Rs7ro0Z_XG_hVV2Y3MvySDCQNdBGE-1642426970-0-gaNycGzNCJE) that cover majority...
We would like to be able to identify operations as: - approved - experimental - private preview - privileged [AB#10844](https://microsoftgraph.visualstudio.com/0985d294-5762-4bc2-a565-161ef349ca3e/_workitems/edit/10844)