I think we’d want the introspect-able range for parameter validation to be an automatic operation as opposed to redundant custom validation checks written in code. My goal was to achieve this in the interim through a parameter validator class with optional upper/lower bound arguments passed for parameters. I do think having this as optional meta-info on the parameters as @wjwwood mentioned as TODO is a better option going forward with perhaps a validation function written in the ROS2 parameters code to protect from parameter changes that violate.
1 Like