The Config System is missing a number of validation checks.
Until these (and probably others) are implemented, it will be possible for users to corrupt the robot's configuration state just by calling the Config System's interface methods.
Missing checks include:
Creating parameters that aren't leaf nodes of the tree,
Creating parameters whose paths contain the names of existing parameters.
Reading interim paths as parameters (although this will almost always fail anyway).
Storing parameter names containing dots.
Setting a range on a parameter whose current value does not satisfy the new range.
(If additional necessary checks are identified, they should be added to this issue)
The Config System is missing a number of validation checks. Until these (and probably others) are implemented, it will be possible for users to corrupt the robot's configuration state just by calling the Config System's interface methods.
Missing checks include:
(If additional necessary checks are identified, they should be added to this issue)