-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redundant service call parameter "node_name" for system_modes services #24
Comments
Thanks, @chcorbato, this is a very valuable observation. This redundancy was indeed also present in the according So you are right, this should be removed from the system mode services as well. |
* Node name is already encoded in the respective topic name of the service #24 Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
* Adapts mode callbacks for nodes and systems (get mode, change mode, get available modes) * part name (system or node) no longer cames from request object, but is coded in the callback #24 Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
* Version bump to 0.3.0 due to API change (mode services) * Adapts system modes exaple documentation to new service format #24 Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
@chcorbato please have a look at PR #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?
The text was updated successfully, but these errors were encountered: