Closed chcorbato closed 4 years ago
Thanks, @chcorbato, this is a very valuable observation. This redundancy was indeed also present in the according lifecycle_msgs/srv/
when we first started this project (before pushing it to github), but was since removed: https://github.com/ros2/rcl_interfaces/pull/39 (October 2018).
So you are right, this should be removed from the system mode services as well.
@chcorbato please have a look at PR https://github.com/micro-ROS/system_modes/pull/31
Hi @norro
This issue is still present in the /feature/rules branch, I'm not sure if a new issue is needed, but It'll be good to apply the solution to that branch as well.
Very good point, I will port it there as well.
@marioney should be ported now. If it causes any issues, please don't hesitate to open further bug reports.
Currently,
system_modes/srv/GetAvailableModes
,system_modes/srv/ChangeMode
andsystem_modes/srv/GetMode
require as parameter thenode_name
. However, the similar services fromlifecycle_msgs/srv/*
do not require to pass that parameter, since the service name/scope already includes it. For example:Maybe that service parameter could be optional, also for system_modes to have a more similar interface to lifecycle?