microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Inconsistent usage of service principal
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
ServicePrincipalsWithAppIdRequestBuilder does not expose the same methods as ServicePrincipalsRequestBuilder. For example, there is no AppRoleAssignedTo in the former, whilst it is in the latter, and https://graph.microsoft.com/v1.0/servicePrincipals(appId='ab7752ff-3c3a-abcd-xyzw-d6c3349bf789')/appRoleAssignedTo works just fine.
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
Start at src/Microsoft.Graph/Generated/BaseGraphServiceClient.cs around line 517, then compare ServicePrincipalsWithAppIdRequestBuilder with ServicePrincipalsRequestBuilder. Check the existing AppRoleAssignedTo surface and the documented servicePrincipals(appId=...)/appRoleAssignedTo endpoint; done means the app-id builder exposes the same supported operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100