microsoft / microsoft/vscode-makefile-tools

Have a way to set the launch target in function of the chosen build target

Open
#254 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
242
Forks
78
PR merge metrics
No merged PRs in 30d

Description

In other words, if I build my app, than I wanna launch my app. If I build my tests, than I wanna launch my tests.
I would propose something like :

"makefile.buildConfigurations": [
        {
            "name": "default",
            "defaultLaunchConfiguration": "nameOfMyAppLaunchConfiguration",
        },
        {
            "name": "test",
            "defaultLaunchConfiguration": "nameOfMyTestLaunchConfiguration",
        }
    ]

OR

"makefile.buildConfigurations": [
        {
            "name": "default",
            "defaultLaunchTarget": "nameOfMyAppLaunchTarget",
        },
        {
            "name": "test",
            "defaultLaunchTarget": "nameOfMyTestLaunchTarget",
        }
    ]

When we change the build target, the launch target gets updated to the specified value. The launch target is not updated when no value is specified.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how build configurations and launch targets are represented and updated in the extension. Compare the two proposed settings approaches and check any existing configuration or launch-target tests and documentation. Done means changing a build target updates its configured launch target, while configurations without a value leave the launch target unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
build-system, developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.