microsoft / microsoft/vscode-cmake-tools
Remove the debugging/running feature with F7 and use the vs-code defaults
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
Firstly: great extension! I use it all the time and I love it. Thanks for putting in the effort.
I have a suggestion though: integrate further with cpptools to automatically create a launch file and/or build tasks instead of having your own custom system with custom shortcuts. I think it would fit better into the vscode way of doing things if you could press F5 to run and so on.
That's all! Thanks.
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 extension's custom F7 debugging and running behavior, then examine how it could integrate with cpptools through launch files and build tasks. Done means the custom shortcut workflow is removed or replaced and standard VS Code defaults such as F5 work for CMake projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, typescript, vscode
- Domain
- build-system, developer-experience, devtools, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100