Derive Messages from Base Classes#230
Conversation
Signed-off-by: Michael Carlstrom <rmc@carlstrom.com>
fujitatomoya
left a comment
There was a problem hiding this comment.
this makes sense to me.
this PR upgrades the inheritance of the generated metaclass to use ROS-specific metaclass logic, improving support for endpoint types and their associated messages in ROS 2 Python code generation.
i would like to have another approval before merge.
christophebedard
left a comment
There was a problem hiding this comment.
I have a minor comment in the other PR, otherwise LGTM
Signed-off-by: Michael Carlstrom <rmc@carlstrom.com>
Signed-off-by: Michael Carlstrom <rmc@carlstrom.com>
Signed-off-by: Michael Carlstrom <rmc@carlstrom.com>
Co-authored-by: Christophe Bedard <bedard.christophe@gmail.com> Signed-off-by: Michael Carlstrom <rmc@carlstrom.com>
|
Pulls: #230, ros2/rosidl#887 |
|
@InvincibleRMC it looks like there's a real test failure in |
|
Ok I found the bug not having |
|
Pulls: #230, ros2/rosidl#887 |
Description
Having messages inherit from a common base class will make it so
Client/Service/ActionClient/ActionServercan automatically infer the generic types they are using. Currently they need to be manually specified.Based on the original issue but the base classes in
rosidl_pycommon.Builds off ros2/rosidl#887
Fixes #215
Is this user-facing behavior change?
It would allow users to isinstance check to determine if an object is a message.
Did you use Generative AI?
Additional Information