RexOps/Rex

Better error handling

Open

#991 创建于 2016年3月11日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Perl (671 star) (218 fork)batch import
help wantedtask

描述

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

贡献者指南

技术栈
无
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
无
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
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.