Open BenjaminMichaelis opened 10 months ago
Thanks for raising this @BenjaminMichaelis
Any chance you can confirm if the url built is as expected by confirming the url string is as expected?
var URL = folder.ToDeleteRequestInformation().URI.OriginalString;
Thanks for raising this @BenjaminMichaelis
Any chance you can confirm if the url built is as expected by confirming the url string is as expected?
var URL = folder.ToDeleteRequestInformation().URI.OriginalString;
From what I can tell? I'm not an expert at reading the url's so I'm not positive, but since the only different is additional call to pass in the id or not and that is what the sdk allows for I'm confused on the needing to check the URL's. I would expect both should work, and the SDK does the heavy lifting for me.
I'm more curious about whether adding root
parameter is necessary in ItemWithPath(root + path)
this is because, the Drives[drive?.Id].Root
already contains root
and adding it twice will result in an invalid path relative to the folder you're trying to address.
I'm more curious about whether adding
root
parameter is necessary inItemWithPath(root + path)
this is because, theDrives[drive?.Id].Root
already containsroot
and adding it twice will result in an invalid path relative to the folder you're trying to address.
The root isn't actually "root", it's the default folder name under the true "root" of which all the files are stored under relatively.
The CustomDriveItemItemRequestBuilder doesn't do what DriveItemItemRequestBuilder can do.
Ex:
With permission.Id being gotten from Graph API already (with value of like
YzowdC5jfHRlbmFubHwtPYFxNWQwNi04NjDzLTRkNzctOWY4OS2mM1JmDMNMIWEzM2P
works fine, butdoesn't work (
ODataError : Item not found
).I expect
DriveItemItemRequestBuilder
to work the same asCustomDriveItemItemRequestBuilder
as the only difference in being able to get one of these types is whether when getting a drive item,ItemWithPath()
orItems[item.Id]
is used andPermissions.DeleteAsync()
exists on both.