TeamAmaze / TeamAmaze/AmazeFileManager
Compression notification doesn't update after initial stats
Open
Nobody has claimed this yet.
Issue-Bug
Issue-Task (low)
Needs-Triage
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
After first few seconds, compression notification doesn't really update to give status of files being compressed or the rate at which they're being compressed.
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
Start by reproducing the compression operation and observing the notification after the initial few seconds. Locate the compression notification entry point, then verify that it reflects the files being compressed and their compression rate throughout the operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100