Guard LC devtools by optional include
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 245
- Forks
- 36
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 4
Description
I'm told this works:
include:
- path: /does/not/exist/or/not/accessible
optional: True
It doesn't work exactly like what i wanted but we might be able to wrangle it...
I wanted something like this
cppcheck:
version: [2.9]
buildable: false
allow_no_access: true
externals:
- spec: cppcheck@2.9
prefix: /usr/workspace/smithdev/devtools/toss_4_x86_64_ib/latest/cppcheck-2.9
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 locating the configuration handling for include entries and LC devtools, then compare the existing optional include example with the desired cppcheck configuration. Determine how optional access should affect an unavailable external tool and define completion around the shown allow_no_access and optional behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100