microsoft / microsoft/OpenAPI.NET.OData
Expanding navigation properties on alternate keys
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 240
- Forks
- 70
- Avg merge
- 7h 59m
- Merged PRs (30d)
- 13
Description
Related to https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/2243
From the documentation at https://learn.microsoft.com/en-us/graph/api/directoryrole-list-members?view=graph-rest-1.0&tabs=http#example-2-get-the-members-of-a-directory-role-using-roletemplateid
It should be possible to list the members of a directoryRole using id or using the roleTemplateId alternate key.
GET /directoryRoles/{role-id}/members
GET /directoryRoles(roleTemplateId='{roleTemplateId}')/members
At moment we do not expand paths with alternate keys even though they may have contained navigation properties. As these maybe be valid paths, we will need to investigate the validity and impact on path expansion across other paths.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the path-expansion logic and compare navigation-property expansion for the id path with the alternate-key directoryRole examples; then assess the validity and impact across other paths. Done means the supported alternate-key navigation paths are defined and covered by appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100