Support 'launch only', and 'debug only' attributes for launching a ROS composition #605
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces a new feature to filter what the debugger attaches to, or just launches.
For example, Debugging ROS2, but not attaching to a rviz or gazebo would look something like the attached
launch.json
file.Similarly if you only wanted to debug a single node in a composition:
Note: VSCode does not track launched ROS nodes, so they have to be manually stopped.