Improve error handling
Registered by
Jo Vermeulen
After a few years, the Uiml.net codebase has grown and been patched upon by different people. This had as a result that the code is not always consistent, clear or efficient. An important problem however is that it is difficult to debug a renderer, knowing what exactly went wrong. From the beginning, we had the convention to return null values, instead of throwing exceptions (in order to keep the renderer going after some mistakes). We should add a number exceptions (e.g. ParseException, RenderException, etc.) and throw them whenever something unexpected occurs, instead of always trying to continue.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for uiml.net-dev
- Implementation:
- Not started
- Milestone target:
- 0.1
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)