microsoft / microsoft/vscode-cpptools
Warn about incorrect include paths in the compile command's file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
For my extension, I'm creating a better Backup Intellisense that parses the compile commands for includePaths which also lets you convert it to exclusive includePath Intellisense.
Doing so shows 88 include paths, in the compile commands file, that were incorrect. They must be not that important since Intellisense still worked.
Would this be considered a bug(or feature request) that the cpptools extension doesn't warn about incorrect include paths in the compile command's file?
Originally posted by @boocs in https://github.com/microsoft/vscode-cpptools/issues/6358#issuecomment-761285903
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 with the compile commands file containing the reported incorrect include paths and review how the extension consumes those paths. Determine how an invalid path should be identified and where a user-facing warning would belong; done means incorrect include paths reliably produce a clear warning without disrupting working IntelliSense.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100