microsoft / microsoft/vscode-cpptools
No includePath is used if a custom browse configuration is received and no c_cpp_properties.json exists
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
With no c_cpp_properties.json, enable a configuration provider so it sends a custom browse config, but then either disable the config provider extension or have it not configured such that no actual custom configuration is sent for a source file.
Bug: No default includePath gets used (defines get used) -- ideally it would fall back to using the recursive includes ${workspaceFolder}/**. This becomes fixed once the custom browse config is no longer received.
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 the case with no c_cpp_properties.json, a configuration provider enabled, and no custom source-file configuration; start by tracing how the custom browse config is received and how default include paths are selected. Done means the recursive ${workspaceFolder}/** include path is used when no actual custom configuration is sent, while defines continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100