Closed sla-ppy closed 7 months ago
This is a super dirty fix to the issue. We essentially duct tape a problem which should definitely be revisited later on!
The reason for this dirty fix is because mVehichleData contains both unicycle and vehicle data, and I am unsure if we want it to stay like that.
I propose that in the new protocol we treat unicycle and vehicle data differently because there are questions to be answered like:
Benefit of the proposal:
Please review my code: @lionkor.
Could I further this topic by suggesting that instead a configuration option be added to specify vehicle names that can be added so they bypass the vehicle limit.
This would be for things like the unicycle as default but can then be expanded to items like cones, bollards, concrete barriers or even pucks.
Could I further this topic by suggesting that instead a configuration option be added to specify vehicle names that can be added so they bypass the vehicle limit.
This would be for things like the unicycle as default but can then be expanded to items like cones, bollards, concrete barriers or even pucks.
I would ask you to make a new feature issue for that, because I'd also like to specify that properly before building it, and I wouldn't want to tack it onto this bug as I want this in the next release.
@sla-ppy btw in documentate unicycle dirty fix
the correct form is document
;)
@sla-ppy btw in
documentate unicycle dirty fix
the correct form isdocument
;)
Fixes #246.