-
Notifications
You must be signed in to change notification settings - Fork 11
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
Document parameters from YAML file required by generate_parameter_library #142
Comments
Can you point to any examples where someone has take this yaml file, and generated such a page? Can you point to a few packages that are actually using this file? |
Hello @rkent , I don't have an example now. I was documenting a package that I am working on and thought that this feature would be very valuable. About the packages that use the generate_parameter_library, almost all (if not all) ros2_controllers use it. Here is the file used by the diff_drive_controller. |
I did a quick scan of rolling, found 'generate_parameter_library(' in CMakeLists.txt for these packages: generate_parameter_library used in <ur_controllers> It would not be hard to located generate_parameter_library in CMakeLists.txt, extract the name and parameters, then display the raw text of the yaml file (with a little bit of text highlighting). Not saying I will do it, but is not a big job maybe a few hours of work. Don't know if the powers-that-be would support that or not. |
Looks like they implemented this feature there. In this case it would only be up to integration |
This proposal outlines the creation of a feature to parse the
.yaml
file required by thegenerate_parameter_library
(if the package uses it) and generate a page with a table or bullet points that describe the parameters necessary for the package. Thegenerate_parameter_library
sets specific requirements for the fields in the.yaml
file, making it easier to translate to a.rst
file with parameter descriptions, including details such asdescription
,default_value
, and values validation.The text was updated successfully, but these errors were encountered: