ros-controls / ros-controls/ros2_controllers

[JTC] Cleanup TODO-List from #320

Open
#944 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

persistent stale
Dominant language
C++
Stars
834
Forks
530
Avg merge
18h 3m
Merged PRs (30d)
19

Description

To keep track of TODOs mentioned with #320:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with joint_trajectory_controller.hpp lines 224-241 and joint_trajectory_controller.cpp lines 164-165, then inspect trajectory_operations.cpp and trajectory.hpp. Determine whether the listed helpers belong in those trajectory files and what RealtimeSubscriber API is available. Done means both remaining unchecked TODOs are resolved and the controller remains consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
robotics
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.