Replace BoundingBox msgs from vision_msgs with internal variants #44
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.
Signed-off-by: Yadunund yadunund@gmail.com
The msg definitions for
vision_msgs::BoundingBox3D
andvision_msgs::BoundingBox2D
have API breaking changes betweengalactic
andhumble
versions. To continue supporting both ROS 2 versions in RMF, this PR updates theObstacle
msg definition to include an internal BoundingBox msg and not rely onvision_msgs
. But the new messages have the same definition as thegalactic
version ofvision_msgs
.See https://github.com/ros-perception/vision_msgs