harababurel/gcsf

Implement Trash directory

Open

#2 opened on Jun 27, 2018

View on GitHub
 (2 comments) (2 reactions) (1 assignee)Rust (94 forks)user submission
enhancementhelp wanted

Repository metrics

Stars
 (2,378 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Intended behavior:

  • The Trash directory should show all files with trashed = true on Drive.
  • Removing a file (unlink) from any directory mark it as trashed.
  • Moving a file (rename) from any directory to Trash should mark it as trashed (f273d25).
  • Removing a file (unlink) from Trash should delete it permanently (bd528c31d8253d9c28d24bf3817f76f864790e23, 11ebeb65443c1516a0e1f31275906cd47e83d130)
  • Moving a file (rename) from Trash to anywhere else should mark the file as not trashed and possibly update its parent.
  • Recursively removing a directory (rm -r) should preserve the hierarchy of its content even when moved to Trash

Contributor guide

Research direction
Study the existing code for rename and unlink operations in the FUSE layer and Google Drive API integration. Focus on how trashed status is tracked and updated.
Tech stack
rust
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65