Repository navigation
Inconsistent behavior with compound configurations depending on both settings.json and launch.json configurations #77782
Description
- VSCode Version: 1.36.1
- OS Version: MacOS 10.14.5
Scenario
Extension user reported a problem with a compound configuration not working correctly with a custom extension using vscode.debug.startDebugging. The extension creates a command that sets up the debugging environment (e.g. starts services) before launching a given debug configuration by name.
Steps to Reproduce
-
Create a new workspace (any target should do).
-
Define a configuration structure similar to this:
settings.json
...
"launch": {
"configurations": [
{ "name": "Config_A", ... }
],
"compounds": [
{ name: "Compound", "configurations": [ "Config_A", "Config_B" ] }
]
}
...
launch.json
...
"configurations": [
{ name: "Config_B" , ... }
]
...
-
From the Debug drop down, select "Compound" and run.
This works. -
Create an extension that runs this line (a workspace must be loaded):
vscode.debug.startDebugging(vscode.workspace.workspaceFolders[0], 'Compound')
This fails with "Configuration 'Compound' is missing in 'launch.json'".
Questions
-
Should step 2 (run from drop down) work? It seems to me it should not:
-
According to this page: https://code.visualstudio.com/Docs/editor/debugging, Tip: If a workspace contains a "launch.json", the global launch configuration is ignored.
-
According to
WorkspaceConfiguration.inspectdocumentation, local values (launch.json) should override global (settings.json). This works strictly as documented. For the provided repro:Workspace.getConfiguration('launch').get('configuration')only returns configurations in launch.json (i.e. arrays are not merged),Workspace.getConfiguration('launch').get('compounds')only returns compound configurations in settings.json (i.e. because launch.json does not define a compounds value). UsingWorkspaceConfiguration.inspectI can verify all configuration values exists and are overriden as intended.
-
-
If Step 2 should work, how to run step 3? i.e. how to use
vscode.debug.startDebuggingto call 'compound' successfully? -
If step 3 should not work, neither should step 2. Correct?
Activity
isidorn commentedon Oct 17, 2019
The issue seems to be here .
Since you want 3) I will rename this issue and it is a fair feature request, which we do not currently plan to tackle.
Thanks
damolina-stripe commentedon Oct 18, 2019
The idea would be for
vscode.debug.startDebuggingto have behavior parity with the Debug dropdown, whatever the proper behavior happens to be. Extension users see it as an extension bug when behavior is not equivalent.Having said that, it is not a P1 bug for sure but would it be possible to update documentation to call out this difference?
isidorn commentedon Oct 18, 2019
I agree that there should be parity. And we will aim for this.
I think updating docs makes sense and we accept PRs in our vscode-docs repository https://github.com/microsoft/vscode-docs
vscodebot commentedon Jan 15, 2020
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
vscodebot commentedon Mar 6, 2020
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding
vscodebot commentedon Mar 6, 2020
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding
vscodebot commentedon Mar 16, 2020
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!