cbarlin / cbarlin/advanced-record-utils
Generate more logging
Open
enhancement
good first issue
help wanted
- Dominant language
- Java
- Stars
- 3
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Description
There should probably be more logging/comment generation in the generated code. The `Merger` doesn't generate any, and `XML` barely does either.
I'm not 100% sure what logs would provide the best "bang-for-buck" either...
Contributor guide
Research direction
Start by inspecting the generated code paths for Merger and XML, since the issue identifies those as having little or no logging or comment generation. Determine which generated operations would benefit most from observability, then define and confirm the scope before making changes. Done means the agreed logging or comments appear consistently in the generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100