microsoftgraph / microsoftgraph/msgraph-metadata
`GET /beta/directory/deletedItems/{directoryObject-id}/microsoft.graph.user` is missing metadata for `ConsistencyLevel` header
Open
Nobody has claimed this yet.
ToTriage
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
The /directory/deletedItems/{directoryObject-id}/microsoft.graph.user endpoint in the beta API doesn't have a ConsistencyLevel header description.
current description
'/directory/deletedItems/{directoryObject-id}/microsoft.graph.user':
get:
tags:
- directory.directoryObject
summary: Get the item of type microsoft.graph.directoryObject as microsoft.graph.user
operationId: directory_GetDeletedItemAsUser
parameters:
- name: directoryObject-id
in: path
description: The unique identifier of directoryObject
required: true
style: simple
schema:
type: string
x-ms-docs-key-type: directoryObject
- name: $select
in: query
description: Select properties to be returned
style: form
explode: false
schema:
uniqueItems: true
type: array
items:
enum:
- id
- deletedDateTime
type: string
- name: $expand
in: query
description: Expand related entities
style: form
explode: false
schema:
uniqueItems: true
type: array
items:
enum:
- '*'
type: string
responses:
2XX:
description: Result entities
content:
application/json:
schema:
$ref: '#/components/schemas/microsoft.graph.user'
default:
$ref: '#/components/responses/error'
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.
Research direction
Locate the beta metadata entry for GET /directory/deletedItems/{directoryObject-id}/microsoft.graph.user and inspect its parameters. Add the missing ConsistencyLevel header description, then verify that the endpoint metadata documents the header consistently with the requested change.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100