Skip to content

Feature request for option to hide / sort launch configurations used by compounds #64624

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

Closed
Hecatron opened this issue Dec 7, 2018 · 5 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality
Milestone

Comments

@Hecatron
Copy link

Hecatron commented Dec 7, 2018

Hi,

One thing I'm using at the moment is compounds within launch.json which is pretty awesome
to launch multiple launch configurations at the same time (such as javascript / .net core etc)

I was thinking it would be useful to have the option to hide or specify a launch configuration's position in the drop down when selecting the debugging profile (so for example you could set it to only show the compounds in the debug window drop down, or specify to move them to the top of the list)

Just as an example

{
   // Use IntelliSense to find out which attributes exist for C# debugging
   // Use hover for the description of the existing attributes
   // For further information visit https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md
   "version": "0.2.0",
   "compounds": [
        {
            // The only thing to show up in the list
            "name": "Debug ASP.Net Core & Chrome",
            "configurations": ["Launch .NET Core", "Launch Chrome"]
        }
    ],
    "configurations": [
        {
            "name": "Launch Chrome",
            "type": "chrome",
            "request": "launch",
            "url": "http://localhost:1111/",
            "webRoot": "${workspaceFolder}/wwwroot",
            "visible": "false" // Defaults to true
            "sortorder": "1"  // Specifies to be at the top of the list if visible
        },
        {
            "name": "Launch .NET Core",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            "visible": "false"
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/bin/Debug/netcoreapp2.1/AspNetCore.Vue.Bootstrap1.dll",
            "args": [],
            "cwd": "${workspaceFolder}",
            "stopAtEntry": false,
            "internalConsoleOptions": "openOnSessionStart",
            "launchBrowser": {
                // Use the seperate chrome debugger profile instead
                // To allow debugging of javascript in the vscode ide
                "enabled": false,
                "args": "${auto-detect-url}",
                "windows": {
                    "command": "cmd.exe",
                    "args": "/C start ${auto-detect-url}"
                },
                "osx": {
                    "command": "open"
                },
                "linux": {
                    "command": "xdg-open"
                }
            },
            "env": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "sourceFileMap": {
                "/Views": "${workspaceFolder}/Views"
            }
        }
    ,]
}
@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality labels Dec 7, 2018
@weinand weinand assigned isidorn and unassigned weinand Dec 7, 2018
@isidorn
Copy link
Contributor

isidorn commented Dec 10, 2018

For now you can edit your launch.json to produce the same effect (by commenting out configuraiotns and reordering them).
Leaving this open as a feature request

@isidorn isidorn added this to the Backlog milestone Dec 10, 2018
@isidorn isidorn removed their assignment Dec 10, 2018
@Hecatron
Copy link
Author

If you comment out a configuration, doesn't this prevent the compound from using it though?

@isidorn
Copy link
Contributor

isidorn commented Dec 10, 2018

@grbd that is correct. I misunderstood what you are exactly trying to achieve.

This could be done by adding an attribute to the launch configuration to make them invisible in the ui, but that they can still be referenced by the compounds. THough noithing on our immediate plan/

@isidorn isidorn self-assigned this Oct 8, 2019
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Oct 8, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 8, 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!

@isidorn
Copy link
Contributor

isidorn commented Oct 11, 2019

We are actually reconsidering this.
Appologies for opening a new issue #82332
You can follow that one for more details

@isidorn isidorn removed the *out-of-scope Posted issue is not in scope of VS Code label Oct 11, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants