Placeholder lost when triggering snippets
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
When having VSCodeVim enabled, all the previously generated placeholders will be lost when a new snippet is triggered. For example, as for the snippet below, which is provided by OrangeX4-HyperSnips
https://github.com/VSCodeVim/Vim/assets/83064277/92a1c2cd-94b0-4dac-bdf5-e7deebed7142
The expected behaviour is that after triggering the second expansion, the placeholder at the end of the line will still be effective.
To Reproduce
Steps to reproduce the behavior:
- Trigger any snippet expansion that generates placeholders
- Trigger another expansion
- The previous placeholders are all lost
- See error
Expected behavior
Previously existing placeholders should not be lost after triggering new expansions.
Environment (please complete the following information):
- Extension (VsCodeVim) version: v1.26.1
- VSCode version: 1.84.0-insider
- OS: Debian trixie
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
No source file, test, or entry point is named in the issue. Start by reproducing the two-step snippet expansion on the stated VSCode and VSCodeVim versions; the work is done when placeholders from the first expansion remain effective after triggering a second expansion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100