Better error handling
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Currently we don't have a proper error handling. We throw exceptions at multiple places, some get caught others not. Also the exceptions are just strings so a proper handling of these exception can't be guaranteed.
To solve this, we need to define a proper way to throw and catch exceptions. We also need to have more detailed error messages for 2 kind of users. One for novice users who don't know the internals and one for powerusers/developers with stacktraces and other interessting stuff.
Some linked issues:
#959 #949 #671 #477 #489 #343
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
No files, tests, or entry points are identified in the issue. Start by reading linked issues #959, #949, #671, #477, #489, and #343 to understand the existing exception paths and requirements; the work is done when exception behavior and separate novice and developer error messages are defined and implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100