microsoft / microsoft/vscode-cpptools
Move use of `console.log` to C/C++ output channel
Open
Nobody has claimed this yet.
internal
Language Service
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
There are a many uses of console.log() that could be output to the C/C++ output channel instead. They currently do not indicate what extension they relate to, so are mysterious to users who see them in the developer tools console output. i.e.:
[Extension Host] provideCustomConfiguration
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 TypeScript sources containing the reported console.log calls and identify the C/C++ output-channel entry point. Update the relevant logging so messages appear in that channel and identify the extension; the issue names no specific file or test, so verify the affected output behavior across the changed uses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100