Equivalent inspection options for ROS Launch files (`--dump-params`, `--nodes` and `--args`)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 155
- Forks
- 182
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 6
Description
Feature request
Feature description
In ROS1, the roslaunch provides a set of options (--dump-params, --nodes and --args) to inspect what's parameters and command lines that ROSLaunch eventually invoke. This is really useful for downstream tool to synthesize the ROS composition for debugging purpose. For example, vscode-ros extension is utilizing it to implement the ROSLaunch debugging feature, which is one of the mostly used functions.
It would be nice to see ROS 2 launch CLI can offer the similar experience, so the downstream tool can do the similar integration for ROS 2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ROS 2 launch CLI and comparing its inspection capabilities with the ROS1 roslaunch options --dump-params, --nodes and --args. Done means defining and implementing equivalent inspection behavior that downstream tools can use to synthesize ROS composition for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100