microsoft / microsoft/vscode-cpptools
Add a C_Cpp.codeAnalysis.include setting (opposite of C_Cpp.codeAnalysis.exclude)?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
The reason for adding a C_Cpp.codeAnalysis.include setting is when you have
parentFolder
- lots of child folders to be excluded
- one folder (or a smaller number) that is desired to not be excluded
That scenario is more work to deal with without some sort of "include" setting. Particularly, when a new child folder is added, then it may have to be added to C_Cpp.codeAnalysis.exclude .
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
Start by reviewing how the existing C_Cpp.codeAnalysis.exclude setting is defined and applied in the extension. Determine the intended precedence and behavior for a new C_Cpp.codeAnalysis.include setting, then verify that the requested parent-folder scenario works without requiring every newly added child folder to be listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100