microsoft / microsoft/vscode-cpptools

[Feature Request] Automatic source file map configuration

Open
#4,950 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger Feature Request
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

This is a feature request for quality-of-life improvement to debugging experience.

When regular Visual Studio is asked to step into function for which it doesn't have code, it opens up a file open dialog to locate the file. Once the user navigates to the directory that matches suffix of the requested file, this directory is automatically added to the solution configuration.

This is particularly useful for code that you don't compile yourself but aquire independently and it is located in a place that is different than original build location.

For example, I regularly debug Qt installed via the Qt installer. It's obviously located in different place than the binaries were built in so I have to configure the source location.

Having a new button "Locate file" in a missing file popup, alongside the "Create file" would be a nice quality of life improvment and would nicely enchance discoverability of the feature:
image

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

No source file or test is named. Start by locating the missing-file popup and the existing source-location or solution-configuration behavior; done means a new "Locate file" action lets users choose the file and automatically adds its matching directory to the configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript
Domain
developer-experience, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.