Motors and devices can be null, caught as errors in RobotConfig instantiation. However, components still try to use these devices and ultimately throw exceptions. These exceptions are caught but can be difficult to debug.
There is a method onboard the config to check and assert null devices. However, this would be easier to implement through various utility functions. (integrating logging etc...)
Motors and devices can be null, caught as errors in RobotConfig instantiation. However, components still try to use these devices and ultimately throw exceptions. These exceptions are caught but can be difficult to debug.
There is a method onboard the config to check and assert null devices. However, this would be easier to implement through various utility functions. (integrating logging etc...)