Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Extension activated despite `capabilities` flag when `virtualWorkspaces` is defined as `false`
See original GitHub issueI’m updating an extension to not support virtual workspaces, but it seems the Debug Session does not respect that capabilities flag.
I mean, I added "virtualWorkspaces": false to the capabilities property in package.json, but whenever I run a debug session and connect to some Virtual workspace, the extension remains enabled.
The only way I could test my extension was packaging and installing the .vsix.
Is debugging really not supported, or should I open an issue for you to take a look?
Thank you
_Originally posted by @alefragnani in https://github.com/microsoft/vscode/issues/123115#issuecomment-846410312_
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah, we do this on purpose. The extension under development is never disabled: https://github.com/microsoft/vscode/blob/main/src/vs/workbench/services/extensions/common/abstractExtensionService.ts#L694
I think current behaviour is OK to run the extension always. I also think giving more priority to capabilities also makes sense. But I am not sure the requested use case -
in order to properly test/validate if the capabilities flag is being respectedis good enough. Because this is a VS Code feature that is implemented/tested by VS Code and may not be a use case for extension.