Add feedback to rejected action goal so the client can know why it was rejected
Open
Nobody has claimed this yet.
backlog
enhancement
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
Feature request
Feature description
When an action goal is sent to a server the server can reject it, but there is no way for the server to tell the client why it was rejected. I think at the very least allowing a string description of why the goal was rejected so the other side can decide what to do next.
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 reading the action goal rejection path in rclcpp and the client/server interfaces involved. Determine how a rejection description should be represented and exposed so the client can receive it; done means rejected goals provide a usable reason without changing accepted-goal behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100