Description
Create a standard for handling error codes throughout the codebase, as many of our errors are not unhandled. This could be in the form of sending a CAN message based on what exactly failed, or a new special way that we can have a better understanding of where and what is happening in the code. This is should be properly researched and planned out
Acceptance Criteria
Handle all errors that could show up in the codebase
Proposed Solution
Mentioned in the description. I think potentially making a new error page on Argos when something happens could be cool too
Description
Create a standard for handling error codes throughout the codebase, as many of our errors are not unhandled. This could be in the form of sending a CAN message based on what exactly failed, or a new special way that we can have a better understanding of where and what is happening in the code. This is should be properly researched and planned out
Acceptance Criteria
Handle all errors that could show up in the codebase
Proposed Solution
Mentioned in the description. I think potentially making a new error page on Argos when something happens could be cool too