The current implementation is riddled with .unwrap() calls at fallible places e.g. when setting up the display of the LXA-TAC. A panic will bring down the whole application without a meaningful error message - even in cases where a degradation of the service quality (e.g. loss of the Display) would be an acceptable error state. A better error handling would identify:
- Critical non recoverable errors - it is okay to bring down the whole application in this case - but with appropriate error messages.
- Critical recoverable errors, where we attempt to recover from the error state or otherwise either move to 1.
- Non Critical errors - we shall never panic in this case but inform the user about the degradation of the service quality
The current implementation is riddled with
.unwrap()calls at fallible places e.g. when setting up the display of the LXA-TAC. A panic will bring down the whole application without a meaningful error message - even in cases where a degradation of the service quality (e.g. loss of the Display) would be an acceptable error state. A better error handling would identify: