microsoft / microsoft/vscode-cpptools
Setting C_Cpp.intelliSenseEngine to "disabled" doesn't work for a workspace folder
Open
Nobody has claimed this yet.
bug
Feature: Configuration
Language Service
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
It only works at the workspace level. If it can't work at the workspace folder level it should have its scope changed in the package.json.
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 inspecting package.json for the declared scope of C_Cpp.intelliSenseEngine and reproduce the setting behavior at workspace and workspace-folder levels. Done means the folder-level setting either disables IntelliSense as expected or has its scope corrected in package.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100