-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add forced deletion #18
Conversation
It looks like the features merged with the other branch too... If you have any suggestions on how to only make it merge the permanent deletion change, I'd be happy to resubmit it if this breaks it in any way. |
I'll review the stream PR first. Once that gets merged in, just rebase this branch and push it up and the only diff should be the As far as permanently deleting a node, I don't see this documented anywhere. How did you find that this endpoint worked? Thanks for the interest in the project! |
Well, I guess the url isn't correct in the implementation and I was mistaken to think it worked (I tried it and it seemed to, but that might've been a mixup), but it does exist on the frontend and probably exists SOMEWHERE on the other host. I'm looking into it now, probably going to have to close this and revert it since I don't think it works :( |
After some digging it seems I was mistaken in thinking that it'd work here. From the developer forums:
I'll close this since it doesn't work. |
Trashed items can be deleted by sending a
DELETE
request tohttps://www.amazon.com/drive/v1/nodes/{id}
, this PR implements it.