rclcpp::LifecycleNode is not on par with rclcpp::Node
Open
Nobody has claimed this yet.
backlog
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
The current lifecycle node lacks quite a bit of functionality (e.g. sub_namespaces) compared to rclcpp's node. They should ideally be en pair.
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
Compare the public rclcpp::LifecycleNode and rclcpp::Node APIs, starting with the reported sub_namespaces gap. Identify the missing functionality and define parity as the completion criterion; the issue names no files or tests, so further project exploration is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100