Logging improvements (structure)
Open
Nobody has claimed this yet.
Contributions are welcome
Estimation - 3 (M)
p3-medium
Technical
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Comes from https://github.com/owncloud/android/pull/4204#issuecomment-1829797533
Better structure would be appreciated. Take a look onto an iOS log:
ownCloud_28_Nov_2023_at_10_11_37.log
globally, it's more readable because request/responses are separated from other logs
So, we can go in that direction and improve it.
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
Review the discussion referenced from pull request 4204 and compare the attached iOS log with the Android logging output. Define the desired logging structure so request and response entries are separated from other logs; the issue does not name Android files or tests, so the implementation scope needs clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100