JakeWharton / JakeWharton/hugo
Add Support For @DebugLog-Behavior On Other Classes
Open
- Dominant language
- Java
- Stars
- 7.9k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Ideally there would be a way to log every class as well (ala Xtrace for iOS). The main use case in mind is adding remote logging/instrumentation to existing, legacy codebases.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name any files, tests, or entry points. Start by reviewing how @DebugLog-Behavior currently applies to classes and how method-call logging is implemented, then determine the scope needed for logging arbitrary existing classes. Done means the proposed support works for other classes and has coverage for the intended legacy-code instrumentation use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100