TeamAmaze / TeamAmaze/AmazeFileManager
Ability to auto-rename existing files.
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.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When copying files to a location where the file name(s) already exist, the existing options are skip and clobber.
Describe the solution you'd like
A clear and concise description of what you want to happen.
There should also be an option to auto-rename the files, e.g. like file(1).txt, which is how ES File Explorer does it.
Describe alternatives you've considered
Use ES File Explorer, although I would love a maintained, non-adware and open source application have this feature.
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
Locate the file-copy logic that handles name collisions and the existing skip and clobber options. Review how a collision choice is exposed in the Android interface, then verify that selecting auto-rename preserves both files with distinct names such as file(1).txt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100