Describe wildcard usage in parameter files#303
Conversation
Wildcards were introduced in ros2/rclcpp#762 And further usage proposed in ros2/rclcpp#1265. Signed-off-by: Jacob Perron <jacob@openrobotics.org>
ivanpauno
left a comment
There was a problem hiding this comment.
Both additions seem like reasonable options (matching all nodes in a namespace, matching all nodes with a name).
I'm not sure if this really has many use cases or not.
If not, I wouldn't add it.
|
Overall LGTM, but I will say that along with ros2/rclcpp#762, ros2/rclpy#370 was introduced. Whatever changes are proposed have to be applied to both client libraries IMHO. |
I'll follow-up to make sure that this happens. |
Signed-off-by: Jacob Perron <jacob@openrobotics.org>
|
IMO, it would be nicer if the implementation for wildcard matching was done in |
I think that's possible, it only requires a refactor of the current implementation. |
Hmm, I think I fiddled with it some time ago. Or @Lobotuerk did. We require extra API, as the wildcard matching cannot happen until we have the fully qualified node name. |
|
Checking ros2/rcl#809, I have some doubts if some things are valid or not:
4 to 9 should be all invalid IMO, |
|
@ivanpauno I completely agree with all your examples. IIUC, the logic added to rcl in ros2/rcl#809 does consider partial matching invalid (e.g. examples 4 to 9). |
|
It might be the case that example 1 isn't considered valid in ros2/rcl#809, I'd have to check. |
We should follow-up. |
|
I didn't notice your comment before. #303 (comment) ros2/rcl#809 expects items from 4 to 9 to be invalid ( Am I missing something? |
|
@iuhilnehc-ynos i think everything is covered as expected on #303 (comment). @jacobperron @ivanpauno i will go ahead to merge this. if anything is missing, let us know! |

Wildcards were introduced in ros2/rclcpp#762
And further usage proposed in ros2/rclcpp#1265.