nextcloud / nextcloud/android-library
Debug/verbose output only in debug builds
Open
Nobody has claimed this yet.
approved
enhancement
- Dominant language
- Kotlin
- Stars
- 105
- Forks
- 99
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 21
Description
Ref https://github.com/nextcloud/android-library/pull/118:
- use proguard to remove debug/verbose output in stable releases
- use another way to check debug (https://github.com/nextcloud/android-library/pull/118#issuecomment-429264155)
- privacy aware stripping, e.g. automatically replace all username, server url, …
- afterwards to the same for client
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 reviewing pull request #118 and its linked discussion about checking debug builds. Identify how debug and verbose output is currently produced, then determine how stable releases should strip it and how privacy-aware removal of usernames and server URLs should work. Done includes applying the approach to the library and then the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100