TeamAmaze / TeamAmaze/AmazeFileManager
Multiple spaces treated as one in root directories
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Description
Multiple spaces in filenames in directories that require ROOT access are displayed as just one space
To Reproduce
When I use other file managers to create a file named a b folder, a b will be displayed on Amaze (multiple spaces become one space). When I create a b in other file managers, a b will also be displayed on Amaze. Then it will cause that files with the same name will be displayed on Amaze, but in fact their names are different.
Screenshots
Reason of This Problem
String[] array = line.split(" +"); in the parseName function in com.amaze.filemanager.filesystem.files.FileUtils treats all multiple spaces as one space
Solution
Improved parsing scheme
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
Inspect the parseName function in com.amaze.filemanager.filesystem.files.FileUtils, focusing on how filenames from root-access directories are split and reconstructed. Verify the behavior with filenames containing multiple spaces and ensure distinct names such as "a b" and "a b" remain distinct when displayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100