microsoft / microsoft/vscode-cpptools
Support additional visualizers directories
Open
Nobody has claimed this yet.
Feature Request
Language Service
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Feature Request
There is https://github.com/microsoft/MIEngine/issues/1049 but not sure if this should be requested here too.
Also note that this could be implemented for both cppdgb and cppvsdbg (which still has no support for an array of natvis https://github.com/microsoft/vscode-cpptools/issues/10917)
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 the linked MIEngine issue #1049 and vscode-cpptools issue #10917, then compare how cppdbg and cppvsdbg currently handle visualizers. Done should mean supporting additional visualizer directories for both backends, including an array of natvis files for cppvsdbg.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100