Debug extension isntance does not reflect code changes
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
Launching the debug task "Build, Run Extension" does not reflect changes to the code.
To Reproduce
- Follow the steps in the contributing guidelines.
- Make any edit to the codebase which affects behavior (for example, removing the
ghcommand) - Click "Build, Run Extension" to launch a VSCode debug instance
- The change is not reflected (for the example of removing the
ghcommand. It still works.)
Expected behavior
Changes should be reflected to allow debugging during development of the extension.
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.25.2
- VSCode version: 1.76
- OS: WSL2 Ubuntu in Windows 10
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 with the contributing guidelines and the configuration behind the "Build, Run Extension" debug task. Reproduce the issue after changing behavior in the codebase, then verify that the launched VSCode debug instance reflects the change and that the example gh command no longer works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100