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

Allow us to extend launch configurations #74636

Closed
pushkin- opened this issue May 30, 2019 · 4 comments
Closed

Allow us to extend launch configurations #74636

pushkin- opened this issue May 30, 2019 · 4 comments
Labels
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

@pushkin-
Copy link

I have a launch.json with two configurations that are basically exactly the same except for the args that I set.

I would like to be able to extend an existing launch configuration and add on just my changes rather than rewriting the entire configuration. E.g.:

{
    "type": "node",
    "request": "launch",
    "name": "A",
    "program": "...",
    "runtimeExecutable": "...",
    ...
},
{
    "name": "B",
    "extends": "A",
    "args": ["arg1", "arg2"]
}
    
@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality labels May 30, 2019
@weinand weinand added this to the Backlog milestone May 30, 2019
@weinand weinand removed their assignment Jun 6, 2019
@weinand weinand added the *out-of-scope Posted issue is not in scope of VS Code label Jun 6, 2019
@vscodebot
Copy link

vscodebot bot commented Jun 6, 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!

@vscodebot vscodebot bot closed this as completed Jun 6, 2019
@pknowles
Copy link

pknowles commented Aug 4, 2022

Can we revisit this? I have giant launch configs. My current workaround is to comment out the arguments to test with but it's a pain to switch between when it could be in a nice dropdown menu.

I really like pushkin-'s idea. It's simple and exactly what I need. It could be implemented at a more generic level, where we could "include" a json block anywhere (although more invasive). This would be really useful for c_cpp_properties.json too, where I am copy/pasting giant blocks of include and search paths.

"environment": [ <project-wide-env-vars> ],
"setupCommands": [ <project-wide-gdb-setup-comands> ],

@mariadb-AlexeyVorovich
Copy link

would be great to have

@TomasHubelbauer
Copy link
Contributor

This would allow different folks on the team to change launch configurations to use either Chrome or Edge based on their preference without generating a Git change.

Current state:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug config",
            "type": "msedge",
            ...
        },

Ideal state:

{
    "extends": "launch.local.json",
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug config",
            ...
        },

launch.local.json:

{
    "configurations": [
        {
            "type": "msedge",
        },

Of course, how to merge the configs would be a discussion to have for sure so both augmenting and completely replacing configuration nodes would be possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

5 participants