add graceful error handling #12

Closed
opened 2025-10-29 08:00:49 +00:00 by foefl · 2 comments
Owner
  • Errors should be communicated as part of the user experience
  • Add an error handling mechanism to:
    • check the result for errors
    • communicate errors by printing to screen (formatted name and message)
    • else: print message about successful execution
- Errors should be communicated as part of the user experience - Add an error handling mechanism to: - check the result for errors - communicate errors by printing to screen (formatted name and message) - else: print message about successful execution
foefl added the
enhancement
label 2025-10-29 08:00:49 +00:00
foefl self-assigned this 2025-10-29 08:00:49 +00:00
foefl added this to the To-Dos project 2025-10-29 08:00:49 +00:00
Author
Owner

requirement: populate error messages via STDERR

requirement: populate error messages via STDERR
foefl moved this to To Do in To-Dos on 2025-11-10 07:42:06 +00:00
Author
Owner
  • add error handling to interface functions
  • return status code in main routine of CLI (defined in interface function)
- [x] add error handling to interface functions - [x] return status code in main routine of CLI (defined in interface function)
foefl moved this to In Progress in To-Dos on 2025-11-10 13:03:25 +00:00
foefl closed this issue 2025-11-10 14:28:28 +00:00
foefl moved this to Done in To-Dos on 2025-11-10 14:28:42 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: EKF-Diagnostic/sensor-anomalies#12
No description provided.