# ROS 2 CLI Arguments Syntax - Feedback Request

**URL:** <https://discourse.openrobotics.org/t/ros-2-cli-arguments-syntax-feedback-request/9942>\
**Category:** ROS General\
**Tags:** ros2\
**Created:** [July 17, 2019, 5:42pm UTC](https://discourse.openrobotics.org/t/ros-2-cli-arguments-syntax-feedback-request/9942 "2019-07-17T17:42:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hidmic](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/hidmic/32/3183_2.png) [@hidmic](https://discourse.openrobotics.org/u/hidmic)\
**Post date:** [July 17, 2019, 5:42pm UTC](https://discourse.openrobotics.org/t/ros-2-cli-arguments-syntax-feedback-request/9942/1 "2019-07-17T17:42:44Z")

</div>

Much like in ROS 1, ROS 2 nodes’ command line is evolving to allow passing parameters via key-value pairs. In this case, however, remapping rules and parameter assignments need further disambiguation. This drove [several discussions](https://github.com/ros2/design/pull/242#issuecomment-51227182), about CLI arguments syntax and how it affects usability, that have yet to conclude.

At this point, we’d very much appreciate your feedback, either on this post or on this [pull request](https://github.com/ros2/design/pull/242), to make sure the end result is comprehensive enough of the varying ways in which you use (or would like to use) this ROS 2 feature - to land in [Eloquent](https://github.com/ros2/ros2/issues/734) -.

---

<div class="post-metadata">

**Author:** ![hidmic](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/hidmic/32/3183_2.png) [@hidmic](https://discourse.openrobotics.org/u/hidmic)\
**Post date:** [July 30, 2019, 9:02pm UTC](https://discourse.openrobotics.org/t/ros-2-cli-arguments-syntax-feedback-request/9942/2 "2019-07-30T21:02:34Z")

</div>

To follow up on this, we’ve settled on a design and [this document](https://github.com/ros2/design/pull/245) accurately reflects it. Thanks to everyone that actively participated in the discussion. Feel free to keep commenting on the design document if you have additional input.