Remove fzf interactive selection for ros2 service call#1244
Conversation
Signed-off-by: Tony Najjar <tony.najjar@dexory.com>
fujitatomoya
left a comment
There was a problem hiding this comment.
lgtm. (as explained, this is not useful.)
|
Pulls: #1244 |
|
Is this also broken in rolling? Should we fix it there as well? |
|
@tonynajjar i think we need to backport this to lyrical, right? this is already there but never really worked. so even if this is kind of behavior change, i think it just gets better for users. |
|
@Mergifyio backport lyrical |
✅ Backports have been createdDetails
|
|
Yes to be backported to lyrical too please 👍 |
Description
After upgrading to Lyrical, I found out that the feature introduced here is not working as expected for
ros2service.When running
ros2 service call <service-name>, fzf pulls out a list of service names although we already specified it:Also plain
ros2 service callwithout a service name does not trigger the fzf list of service names:Aside for the bug, I currently can't see a nice UX for
ros2 service callwith fzf because currently the command is executed directly after the fzf selection but forros2 service callmore often than not, the user wants to specify the values in the request which is currently not possible. This ties with #1184For this reason I propose we remove this functionality that does not work until we can find a clean fix and UX
Fixes # (issue)
Is this user-facing behavior change?
Did you use Generative AI?
Additional Information