In the progress of migrating ROS1 to ROS2, @HenryLeC has determined there is quite a difference between the semantics for creating parameters in ROS1 and ROS2. As such, there needs to be an effort to going through each package and ensuring that their parameter format is coherent with the ROS2 specification. Moreover, if there aren't parameters in a certain package, but it seems logical for there to be so, then it should also be added.
There have been talks about using mrobosub_lib to handle some preprocessing of params to make it easier to use within other packages. This might also be a good chance to investigate that.
In the progress of migrating ROS1 to ROS2, @HenryLeC has determined there is quite a difference between the semantics for creating parameters in ROS1 and ROS2. As such, there needs to be an effort to going through each package and ensuring that their parameter format is coherent with the ROS2 specification. Moreover, if there aren't parameters in a certain package, but it seems logical for there to be so, then it should also be added.
There have been talks about using
mrobosub_libto handle some preprocessing of params to make it easier to use within other packages. This might also be a good chance to investigate that.