Skip to content

Trash feature instead of permanent delete #543

Description

@BaccanoMob

Is your feature request related to a problem? Please describe.
If you accidentally delete something you shouldn't when you multi select (or any other case as well).

Describe the solution you'd like

  • Delete should move items to .trash in the root folder of the source. If .trash does not exist, it creates one.

  • Trash Icon should be near this icon, so on clicking you get the current source's trash contents (aka moves to .trash folder). If you are already in trash folder, then clicking that icon again should prompt for emptying the trash. If .trash does not exist, it creates one and moves to that folder.
    Image

  • If createUserDir: true then .trash is at every user directory (aka another user cant look at your trash and vice versa) instead of root folder.

  • Deleting items in trash leads to permanent delete.

  • Option to restore the item to its original state. In case the folder the item was present is deleted at a later stage, then prompt folder/path does not exist or similar message. Then you must manually move out from the trash folder to restore.

  • Clean up trash settings every x days or disable it set in config.yaml.

  • Option to disable this feature in the settings. Not sure if it should under global settings (like enableThumbnails or resizePreview) or under userDefaults. So a user can still permanent delete if they want to.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions