-
Notifications
You must be signed in to change notification settings - Fork 227
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
Validate parameter names #380
Comments
I want to contribute to this one |
@suab321321 please feel free to do so and open a pull request if you have any questions or want early feedback. |
I have started going through code,will update you soon |
@nuclearsandwich Do I have to implement this in rcl reposiroty like the ones used for rcl/validate_topic_name,and then using the c api I need to implement this in rospy ,am I correct? |
Yes, that would be a good approach.
AFAIK that is correct. |
I agree, rules for parameter naming aren't clear now. We should wait until we start implementing ros2/design#241. |
Okay I will wait for it. |
@jubeira are parameters rules clear now..should I start |
There is not progress in that discussion at the moment. |
Feature request
Validate parameter names on declaration.
The current name validation is simply a non-empty check.
Feature description
Complete constraints for parameter names TBD.
Name validation should enable to reject parameters when their name.
Implementation considerations
Nodes and topics have name validations, but parameters don't.
Following the implementation for node names and topics, it would make sense to implement the solution at RCL level and use that functionality in
rclpy
andrclcpp
. See topic and service names design doc for reference.The text was updated successfully, but these errors were encountered: