microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Naming are making things worse
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Hi,
MS Graph doesn't have enough documentation and the sdk naming is making things worse. I don't know what happened here, but it is the first time I see such a counter intuitive thing in Microsoft packages, this name is strange and not readable and not understood GetAllSites.GetAsGetAllSitesGetResponseAsync . I think it is missing one more GetAsGetAllAs... at the end
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 by reviewing the generated member named GetAllSites.GetAsGetAllSitesGetResponseAsync and the 22-comment discussion for the naming concern. The issue does not identify a source file, test, or agreed replacement; done would require a decided naming change and confirmation of the resulting SDK API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100