Error in the API driver: parent.delete does not always return http 404 when parentId is not a valid identifier

Question

I just found a strange error in the parent.delete file in the API driver.

I am trying to remove a nonexistent parent link for a given file with these parameters:

fileId = validExistingFileId parentId = nonExistingParentId 

By a non-existing parent, I mean an identifier that causes a 404 error when requesting it using File.get

I have two different results: when nonExistingParentId is something that doesn’t even look like id, say 642187, I get my 404. But when it looks something like a valid id, I got a 204 response that would be the requested answer if parentId really referred to a file on my disk.

I know this is not very clear, so if a Google person wants to take action on this behavior, I’ll be happy to give him the specific identifiers I tried

EDIT

Perhaps I need to clarify a bit.

I would like to know if it is possible to get an API error if parentId or fileId refer to an unused resource in Google Drive, which does not match my process.

And there is something for downvoters here that I have never seen to reply or comment google-drive-sdk : SO is the only access point to support Drive API, even if I still have not received a response from google regarding most of my questions. Using SO as bug tracking may not be one of Google’s best practices, but who am I to change that? Therefore, please think twice before closing / tilting issues related to the Disk.

Best wishes