TeamAmaze / TeamAmaze/AmazeFileManager
Corrupt-delete file
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
To delete files in a non-recoverable way. You sure can delete a file, but it just gets marked as re-writable.
Describe the solution you'd like
A delete-feature that consists in injecting in the soon-to-be-deleted file random text in it, and then delete. Corrupt-delete
Describe alternatives you've considered
none
Additional context
In this way the file that get deleted is lost forever, corrupted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the current file-delete flow in the Android app, then investigate storage targets and platform limitations before defining acceptance tests for overwriting followed by deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100