Remove Command's knowledge of its own keybindings #21605

Closed
opened 2026-01-31 07:49:23 +00:00 by claunia · 0 comments
Owner

Originally created by @PankajBhojwani on GitHub (Apr 30, 2024).

Originally assigned to: @PankajBhojwani on GitHub.

Description of the new feature/enhancement

As we move to implementing Action IDs and referring to Commands with their IDs everywhere, it no longer makes sense for a Command to have knowledge about its own keymappings (let the Action Map handle that, especially with all the layering involved)

Proposed technical implementation details (optional)

Remove the keymappings array from Command, currently every place that we query a Command for its keys also has access to the ActionMap, so those places should query the ActionMap for the keys of that Command instead

Originally created by @PankajBhojwani on GitHub (Apr 30, 2024). Originally assigned to: @PankajBhojwani on GitHub. # Description of the new feature/enhancement As we move to implementing Action IDs and referring to Commands with their IDs everywhere, it no longer makes sense for a Command to have knowledge about its own keymappings (let the Action Map handle that, especially with all the layering involved) # Proposed technical implementation details (optional) Remove the keymappings array from `Command`, currently every place that we query a Command for its keys also has access to the ActionMap, so those places should query the ActionMap for the keys of that Command instead
claunia added the Issue-TaskNeeds-Tag-FixProduct-TerminalArea-CodeHealth labels 2026-01-31 07:49:24 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21605