Move example messages out of std_msgs #89
Assignees
Comments
This was referenced May 18, 2020
tfoote
added a commit
that referenced
this issue
May 18, 2020
Followup to #89 Signed-off-by: Tully Foote <[email protected]>
tfoote
added a commit
that referenced
this issue
May 18, 2020
) * Add deprecation messages to all messages now in example_interfaces Followup to #89 Signed-off-by: Tully Foote <[email protected]>
|
Done in a combination of #116 and ros2/example_interfaces#11 |
ghost
mentioned this issue
|
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/soss-a-whole-new-approach-to-your-ros-1-ros-2-bridge/17040/18 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a follow up to the Aggregate Foxy Message API Review
Followup to: https://github.com/ros2/common_interfaces/pull/86/files#r392505128
We should look at moving any of the messages that are not actually standard to something more like
example_msgsthis will set expectations more clearly.This could have wide ranging effects and it might be worth adding explicit warnings into the generators to help with the migration process.
The text was updated successfully, but these errors were encountered: