Skip to content

Conversation

@takluyver
Copy link
Member

When users bind custom shortcuts to actions coming from extensions, the shortcuts can be loaded before the extensions, so we need to allow defining a shortcut for an action that doesn't exist yet.

Closes gh-3549
Closes gh-2954

When users bind custom shortcuts to actions coming from extensions, the
shortcuts can be loaded before the extensions, so we need to allow
defining a shortcut for an action that doesn't exist yet.

Closes jupytergh-3549
Closes jupytergh-2954
@takluyver takluyver added this to the 5.5 milestone Apr 24, 2018
@takluyver
Copy link
Member Author

I slipped a few Javascript improvements in while I was touching this file - mostly not relying on for (var key in obj) style iteration, which is well known as a potential source of problems. Since underscore was already used in this file, I relied largely on its _.forEach() function.

@takluyver
Copy link
Member Author

@parmentelat has confirmed that this fixes the issue they saw.

@takluyver takluyver merged commit 9a3e8ca into jupyter:master Apr 27, 2018
@takluyver takluyver deleted the i3549 branch April 27, 2018 10:35
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

question about extension-defined actions Can't add keyboard shortcuts to actions of extension

1 participant