Expose TypeHash and TypeDescription on generated types
Nobody has claimed this yet.
- Dominant language
- EmberScript
- Stars
- 26
- Forks
- 68
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 1
Description
Feature request
Feature description
The C generated code for types exposes this info, we need to bridge it through the generated python types.
An initial aborted attempt was at https://github.com/ros2/rosidl_python/pull/191
Related to ros2/ros2#1159
Implementation considerations
Access to the type_description_interfaces types at this stage. There is rosidl_runtime_c versions - maybe we move some implementation up to rclpy where the message types will be available?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the aborted rosidl_python pull request 191 and the generated Python type path, then compare it with the existing C-generated TypeHash and TypeDescription support. Check the availability of type_description_interfaces and the roles of rosidl_runtime_c and rclpy. Done means the generated Python types expose equivalent type information with an agreed implementation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100