You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IDL is the "base" message schema format for ROS2, and it's possible that a user may produce an IDL schema for a message without first defining a .msg schema first.
I think the best approach for this would be to define a function that translates an IDL schema into a RosMsgField[], extending the set of supported types in RosMsgField as necessary.
IDL is the "base" message schema format for ROS2, and it's possible that a user may produce an IDL schema for a message without first defining a
.msg
schema first.I think the best approach for this would be to define a function that translates an IDL schema into a
RosMsgField[]
, extending the set of supported types in RosMsgField as necessary.There is already a lark grammar for parsing the ROS2 subset of IDL available here, which is nice because it gives us a clear subset of the full IDL spec to support.
The text was updated successfully, but these errors were encountered: