Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate : Incomplete Path Parameters in TS #11

Closed
Tracked by #96
rkodev opened this issue May 30, 2022 · 9 comments
Closed
Tracked by #96

Investigate : Incomplete Path Parameters in TS #11

rkodev opened this issue May 30, 2022 · 9 comments
Assignees
Labels

Comments

@rkodev
Copy link
Contributor

rkodev commented May 30, 2022

Path generation in TS SDK seems to be missing some request builder properties

Example : https://docs.microsoft.com/en-us/graph/api/ediscovery-legalhold-delete?view=graph-rest-beta&tabs=go

ediscovery is missing in the RequestBuilder

const graphServiceClient = GraphServiceClient.init({authProvider});


const result = async () => {
	await graphServiceClient.compliance.ediscovery.casesById("case-id").legalHoldsById("legalHold-id").delete();
}
@rkodev
Copy link
Contributor Author

rkodev commented May 30, 2022

cc @nikithauc @baywet

@baywet
Copy link
Member

baywet commented May 30, 2022

This API being under beta and this SDK being generated only for v1 I'd say this is expected? Unless the raptor process is generating a beta SDK on the fly?

@rkodev
Copy link
Contributor Author

rkodev commented May 30, 2022

@baywet Had missed that, I'll investigate how the beta snippets were extracted when only v1 were specified in the E2E pipeline

@baywet
Copy link
Member

baywet commented May 30, 2022

no worries, besides that aspect, the path item is in the beta OpenAPI description at the moment '/compliance/ediscovery/cases/{case-id}/legalHolds/{legalHold-id}' and should get generated for.

@rkodev rkodev self-assigned this May 30, 2022
@rkodev
Copy link
Contributor Author

rkodev commented May 30, 2022

@baywet Another example generated from v1

Sample Link : https://docs.microsoft.com/en-us/graph/api/accessreviewinstance-batchrecorddecisions?view=graph-rest-beta&tabs=typescript

pendingAccessReviewInstancesById is missing from MeRequestBuilder

const authProvider = new AzureIdentityAuthenticationProvider(new ClientSecretCredential("tenantId", "clientId", "clientSecret")); 


//THIS SNIPPET IS A PREVIEW FOR THE KIOTA BASED SDK. NON-PRODUCTION USE ONLY
const graphServiceClient = GraphServiceClient.init({authProvider});

const requestBody : BatchRecordDecisionsPostRequestBody = {
	decision : "Approve",
	justification : "All principals with access need continued access to the resource (Marketing Group) as all the principals are on the marketing team",
	resourceId : "a5c51e59-3fcd-4a37-87a1-835c0c21488a",
};

async () => {
	await graphServiceClient.me.pendingAccessReviewInstancesById("accessReviewInstance-id").batchRecordDecisions.post(requestBody);
}

@baywet
Copy link
Member

baywet commented May 30, 2022

In this specific case "pendingAccessReviewInstances" is not present in the CSDL, all what's left are annotations trying to target it to say it's deprecated. I do think it's a separate issue from the one in the original post and should be looked into separately.

@rkodev
Copy link
Contributor Author

rkodev commented May 30, 2022

@baywet Moved the second sample to a separate issue here microsoftgraph/msgraph-sdk-typescript#108

This current issue to be addressed in raptor

@baywet
Copy link
Member

baywet commented Jan 26, 2024

transferring to beta
this path is available here (on the SDK)
@rkodev is the issue for snippets generation?

delete(requestConfiguration?: RequestConfiguration<object> | undefined) : Promise<void>;

@baywet baywet transferred this issue from microsoftgraph/msgraph-sdk-typescript Jan 26, 2024
@rkodev
Copy link
Contributor Author

rkodev commented Jan 9, 2025

Closing this issue as its resolved in version v1.0.0-preview.33

@rkodev rkodev closed this as completed Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants