More ROS1-like tab-completion for ros2topic / ros2service
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 262
- Forks
- 228
- Avg merge
- 23h 15m
- Merged PRs (30d)
- 12
Description
Description
In ROS 1, bash completion after rostopic pub /topic suggested the topic type, and after rostopic pub /topic type suggested the message template.
I think this behavior was very convenient. Even though the command has more parameters that could be added.
I don't know if it's possible implementation-wise, but it'd be great to pretend for autocompletion that topic name can only be followed by type and topic type can only be followed by message prototype.
Motivation
Make ros2 CLI more user-friendly.
Design / Implementation Considerations
I know there was recently some motion with fzf, but I haven't tried myself yet, so I can't comment on whether it solves this request or not.
Additional Information
No response
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
Start by inspecting the ros2topic and ros2service tab-completion entry points and the existing fzf-related completion work mentioned in the issue. Compare their current suggestions with the ROS 1 behavior for publishing topics and services. Done means the relevant commands suggest the type and then the message prototype without preventing other supported parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100