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

DebugConfigurationProvider: support to return "compounds" #37193

Closed
atian25 opened this issue Oct 31, 2017 · 2 comments
Closed

DebugConfigurationProvider: support to return "compounds" #37193

atian25 opened this issue Oct 31, 2017 · 2 comments
Assignees
Labels
api debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@atian25
Copy link

atian25 commented Oct 31, 2017

  • VSCode Version: 1.17.2
  • OS Version: Mac
  1. DebugConfigurationProvider should support compounds
  2. allow hidden or sort order at debug configuration drop list.

image

We only want to show user: Egg Debug and Egg Debug with brk(which is compounds)

so feature request is either provide a hidden property for "Egg Master", "Egg Agent", "Egg Worker", or compounds should show at top.

{
  // Use IntelliSense to learn about possible Node.js debug attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Egg Debug",
      "runtimeExecutable": "npm",
      "runtimeArgs": [ "run", "debug" ],
      "console": "integratedTerminal",
      "restart": true,
      "protocol": "auto",
      "port": 9999
    },
    {
      "type": "node",
      "request": "launch",
      "name": "Egg Master",
      "runtimeExecutable": "npm",
      "runtimeArgs": [ "run", "debug", "--", "--inspect-brk" ],
      "console": "integratedTerminal",
      "restart": true,
      "protocol": "inspector",
      "port": 9229
    },
    {
      "type": "node",
      "request": "attach",
      "name": "Egg Agent",
      "restart": true,
      "protocol": "inspector",
      "port": 5800
    },
    {
      "type": "node",
      "request": "attach",
      "name": "Egg Worker",
      "restart": true,
      "protocol": "inspector",
      "port": 9999
    }
  ],
  "compounds": [
    {
      "name": "Egg Debug with brk",
      "configurations": [ "Egg Master", "Egg Agent", "Egg Worker" ]
    }
  ]
}

move from #34668 (comment)

@vscodebot vscodebot bot added the debug Debug viewlet, configurations, breakpoints, adapter issues label Oct 31, 2017
@weinand weinand changed the title [Feature Request] DebugConfiguration improve Support to return "compounds" from DebugConfiguration.provideDebugConfigurations Oct 31, 2017
@weinand weinand added the feature-request Request for new features or functionality label Oct 31, 2017
@weinand weinand added this to the Backlog milestone Oct 31, 2017
@weinand weinand changed the title Support to return "compounds" from DebugConfiguration.provideDebugConfigurations DebugConfigurationProvider: support to return "compounds" Oct 31, 2017
@weinand weinand added the api label Sep 11, 2018
@philliphoff
Copy link
Member

@weinand The linked issue #50605 was closer to my scenario but was closed as a dupe of this one. I would like to be able to resolve a single debug configuration from launch.json into multiple debug configurations. That is, I would like the option of DebugConfigurationProvider.resolveDebugConfiguration() returning an array of DebugConfiguration objects, including ones which may not exist in launch.json (i.e. that are completely generated).

This would be useful in cases where there is an orchestration of processes that need to be performed before it is known how many and which processes are to be debugged.

@weinand weinand added the *out-of-scope Posted issue is not in scope of VS Code label Oct 14, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 14, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api debug Debug viewlet, configurations, breakpoints, adapter issues 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

3 participants