Absolutely, I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git. I did for so many and this file will get its turn soon.
Absolutely, I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git. I did for so many and this file will get its turn soon.
The order is so important and that the order of receiving the information over the CANBus which going to be used the same order everywhere even in Models and Views. To be clarified, please confirm. 1 - The order is changed and has been implemented correctly in the recent modification of the class. 2 - I expect to see later in a code review the correct order as has been defined in the "message list" excel sheet as below :
This is done in the first if and else statements in this function. 15000 steps is assigned and in this function if the current position to the target position is less than 15000 steps, it will assign the target to it.
Should indicate the return type and what is returned when. if init() changes, this function will behave differently, but it won't be reflected in the documentation
Absolutely, I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git. I did for so many and this file will get its turn soon.
Absolutely, I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git. I did for so many and this file will get its turn soon.
