microsoft / microsoft/gctoolkit
Should we throw a better exception instead of logging, eating and returning a null object in GCToolkit main class
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
Should we throw a better exception instead of logging, eating and returning a null object?
Originally posted by @karianna in https://github.com/microsoft/gctoolkit/pull/252#discussion_r1068699799
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
The issue identifies the GCToolkit main class and links to a discussion in pull request #252. Read that entry point and the linked discussion first, then trace the current logging, null-return, and caller behavior; no test is named, so completion requires agreeing on and verifying the intended exception behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100