microsoft / microsoft/vscode-cpptools
Improve "Add configuration" behavior when not using the language service's "Build and debug active file"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Bug type: Language Service
Describe the bug
- OS and Version: Windows 11
- VS Code Version: 1.60.1
- C/C++ Extension Version: 1.6.0
If launch.json already exists and customers add a new configuration, the "program" and "MIDebuggerPath" properties are not automatically set:
When selecting a configuration for the first time, however, the configurations are "smarter"-- everything is automatically filled in and the customer shouldn't need to edit the properties/values. I believe these are coming from the cpptools Task Provider?
Can we always use the "smarter" configurations?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this in VS Code on Windows with an existing launch.json, then add a new configuration and compare it with the first-time configuration flow. Trace the C/C++ extension's configuration and task-provider entry points to determine why program and MIDebuggerPath are omitted. Done means both properties are populated automatically in the added configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100