microsoft / microsoft/vscode-cpptools
Add a command to perform automatic data collection for bug reporting
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
A command could be added to collect the following:
- Contents of current configuration in
c_cpp_properties.json - Output of the
Log Diagnosticscommand - All
C_cpprelated settings (or all VS Code settings?) - Contents of C/C++ output channel (may require preserving what is output to it, if it's not readable).
- others?
.. and provide guidence on providing that information by opening an issue on github.
Guidance on github could refer users to running this command and including that information when opening an issue.
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 requested data sources: c_cpp_properties.json, the Log Diagnostics command, C/C++ settings, and the C/C++ output channel. Clarify the command's scope, how output should be preserved, what additional data is needed, and how GitHub issue guidance should direct users. Done means the requirements and collection flow are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100