-
Notifications
You must be signed in to change notification settings - Fork 547
Handle ROS 2 types properly #883
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
Conversation
Hey @scottbell, thanks for the PR! This looks more complete than my previous implementation in #840. I'll give this a shot today in my workspace which has experienced some of these issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change worked in my workspace that previously was running PR #840, so this LGTM. Code looks reasonable to me - thanks!
Thank you for testing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me as well -- just some minor comments
I think ROS 2 needs float32 or float64 if I recall correctly? |
Public API Changes
None
Description
Handle ROS2 types properly when building type definitions. Don't crash when handling unknown types. Added test coverage for
objectutils
.Fixes #834 #822 #821