-
Notifications
You must be signed in to change notification settings - Fork 510
Duplicate commands registered #3320
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
Comments
I added that while knowing nothing about how VS code extensions work so I'm not too surprised I made a mistake. What's the correct way to do this? The purpose of my change was to add buttons for those built-in actions because people who are used to ISE are used to having buttons for moving the console around. |
You can just make your own command and then register it which just calls the built-in command. So you'd define
|
@MartinGC94 Do you want to fix this? That'd be awesome. It was on my to-do list but not something I was going to get to today. I can assign to you if you'd like 😁 |
@andschwa sure although I probably won't look at it today either. |
Fixes #3320 by adding extension commands that call the built-in commands.
Upon startup see these errors in the log :
The reason for this is because you define the commands here : https://github.com/PowerShell/vscode-powershell/blob/master/package.json#L285
using the command IDs
workbench.action.positionPanelLeft
andworkbench.action.positionPanelBottom
. But these are the command IDs used by VS Code : https://github.com/microsoft/vscode/blob/main/src/vs/workbench/browser/parts/panel/panelActions.ts#L100so it sees that there's duplicate commands and throws the error (which admittedly isn't actually accurate in this case).
Given that it doesn't seem like you actually try to define this action in your extension currently these commands should be removed from your package.json since currently they aren't actually doing anything. (or given a different command ID and then just have that command call the workbench one if you still want this to show up in the contributions section of the gallery)
The text was updated successfully, but these errors were encountered: