RexOps/Rex

Better error handling

Open

#991 opened on Mar 11, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Perl (671 stars) (218 forks)batch import
help wantedtask

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

Tech stack
None
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review linked issues #959, #949, #671, #477, #489, #343 to understand existing error handling patterns. The issue proposes defining custom exception types and splitting error messages for novice and power users. Look for any existing discussions or partial implementations in those issues. Since the repository uses Perl, consider how to implement exception classes in Perl (e.g., using Try::Tiny or Exception::Class). The issue lacks details on the specific error structure, so further clarification from maintainers may be needed.