Skip to content

Automatically merge in new keybindings #2566

@richardszalay

Description

@richardszalay

Description of the new feature/enhancement

When new key binding actions are added (eg. openNewTabDropdown in 0.4.2382.0), they're not particularly discoverable for upgrading users since they're not added to an existing settings file. It would be nice if new key binding actions were automatically added if they don't conflict with other bindings (and this behavior would probably need to be optional)

Proposed technical implementation details (optional)

Unclear, and I appreciate that this is much more difficult than it first appears since you'd really need to take into consideration what version they were on in order to determine which key binding actions are new and which were simply removed by the user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingResolution-DuplicateThere's another issue on the tracker that's pretty much the same thing.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions