microsoft / microsoft/vscode-cpptools

Add a C_Cpp.codeAnalysis.include setting (opposite of C_Cpp.codeAnalysis.exclude)?

Open
#8,808 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Feature: Code Analysis Language Service more votes needed
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

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 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.