Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeymapExtensions handling still needed? #121861

Closed
isidorn opened this issue Apr 21, 2021 · 4 comments
Closed

KeymapExtensions handling still needed? #121861

isidorn opened this issue Apr 21, 2021 · 4 comments
Assignees
Labels
debt Code quality issues extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Apr 21, 2021

Refs: #119463

I noticed that there we are having some special code for checking conflicts in keymap extnesions https://github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/extensions/common/extensionsUtils.ts#L26

I believe this is no longer needed and we could just do the following:
WHen a user installs a keymap extension that we show a modal dialog that he already has one installed and if he is sure what is he doing and offer to disable the other one. If he says yes, we proceed.

I think that would be a clenaer solution than having an Keymap workbench contribution which handles an obscure case of users having multiple keymap extensions.

Not sure who is the owner, based on blame assigning to @chrmarti and @sandy081

@isidorn isidorn added the debt Code quality issues label Apr 21, 2021
@chrmarti
Copy link
Contributor

Moving the user interaction closer to the user's decision to install a second keymap extension makes sense. Not sure if that will cover all cases (like when installing all in extensions.json), but it might be just enough because it covers the most important case.

@sandy081 Is this something you could implement? (Removing the current code should not be much work.)

@sandy081
Copy link
Member

I agree that moving the decision closer to user interaction is good and makes sense. But I feel that existing check is still needed as extensions can come in from multiple other sources

@sandy081 sandy081 added extensions Issues concerning extensions feature-request Request for new features or functionality labels Apr 22, 2021
@sandy081 sandy081 added this to the Backlog milestone Apr 22, 2021
@isidorn
Copy link
Contributor Author

isidorn commented Apr 22, 2021

Yes, but that is a corner case. Two keymap extensions coming from the other source. In reality how many times do you think that happened?
I think this was much more important while VS Code was an up and coming product. Now we are established and keymap extensions are not as important as they were before since we dictate the keybindings.

Due to the above I suggest to simply remove this in insiders and if 1 user complains feel free to take it back. I think that nobody will even notice it.
Of course having the check after installing would be nice.

@sandy081 sandy081 modified the milestones: Backlog, May 2021 Apr 22, 2021
@egamma egamma modified the milestones: May 2021, June 2021 May 24, 2021
@sandy081 sandy081 modified the milestones: June 2021, Backlog Jun 30, 2021
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Dec 6, 2022
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debt Code quality issues extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

5 participants