Operations for `/users/{user-id}` contains links to intune instead of user
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- api
Research direction
Start by locating the metadata source that generates the /users/{user-id} operations and compare its GET, PATCH, and DELETE documentation links with the corresponding user URLs in the issue. Done means those three operations link to the user documentation rather than the Intune MAM documentation; inspect the generation or validation workflow before changing the source.
Written by the indexing model from the issue text.
Description
GET, PATCH and DELETE operations for /users/{user-id} path contains weird links to the documentation
https://learn.microsoft.com/graph/api/intune-mam-user-get?view=graph-rest-1.0
https://learn.microsoft.com/graph/api/intune-mam-user-update?view=graph-rest-1.0
https://learn.microsoft.com/graph/api/intune-mam-user-delete?view=graph-rest-1.0
Correct ones are
https://learn.microsoft.com/graph/api/user-get?view=graph-rest-1.0
https://learn.microsoft.com/graph/api/user-update?view=graph-rest-1.0
https://learn.microsoft.com/graph/api/user-delete?view=graph-rest-1.0
It can be confusing for developers who are not familiar with the Graph API.
I know that everything is auto-generated, but some validations would be really useful to avoid such problems.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoftgraph/msgraph-metadata
-
ToTriage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoftgraph/msgraph-metadata#1192 ·
-
ToTriage
Difficulty 3/5 1-2 days Newbie friendliness 72/100
microsoftgraph/msgraph-metadata#1193 · 2 comments ·
-
ToTriage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoftgraph/msgraph-metadata#1169 · 1 reaction ·
-
ToTriage
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoftgraph/msgraph-metadata#1166 ·
-
machine OpenToTriage
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoftgraph/msgraph-metadata#1143 ·
All issues in microsoftgraph/msgraph-metadata
Similar issues
-
area/sessions comp/agent P2 tool/skills type/perf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#117788 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·