-
Notifications
You must be signed in to change notification settings - Fork 164
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
Load a message or request from a yaml file (or standard input) #842
Comments
this sounds reasonable to me. it would be useful. |
I noticed that the last argument is optional. For example, the following is valid.
Should we add an option like
|
Yes, definitely. |
Using vscode, this could be achieved with the following command. export EDITOR="code --wait"
cat foo.yaml | vipe | tee tmp.yaml | ros2 topic pub foo std_msgs/Header --stdin; mv tmp.yaml foo.yaml |
Interesting. I have never used ROS 1, but according to the wiki it seems that
Given the problem statement:
Would you consider to also add the |
Feature request
Feature description
I want to load a message/request from a yaml file, not from the command line. The benefits of this would be similar to #753.
Targets are
In my opinion, it would be neat to be able to do the following
cat foo.yaml | ros2 topic pub <topic_name> <msg_type>
Implementation considerations
This maybe conflicts with the functionality of #753. Similar functionality may be achieved with
cat foo.yaml | vipe | tee foo.yaml | ros2 topic pub <topic_name> <msg_type>
.The text was updated successfully, but these errors were encountered: