-
Notifications
You must be signed in to change notification settings - Fork 28
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
Return path to trashed item #38
Comments
I also think this would be a great addition! Maybe also exporting home_trash() in order to be able to query it without having to delete something. I don't mind doing the change myself. |
Should we also return the removed item path in |
Feel free to do what you have to, making a breaking release (with corresponding semver change) is not a problem. Let's be sure we return some type like |
Not sure if I fully understand you. Could you describe a situation in which a trash item is handled by multiple files? |
I don't know all possible implementations nor can I predict the future. In a situation like this, it's a good idea to have a custom type that can act like a |
I have implemented returning |
It would be a great addition to this crate to know what the destination path of the trashed item. Can't think of a better way than returning it after calling
delete()
.The text was updated successfully, but these errors were encountered: