Detect and warn user about badly supported VSCode settings
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
There are a few VSCode settings that VSCodeVim doesn't quite play nice with (#4439). We should, on startup, realize this and let the user know.
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 reading issue #4439 to identify the VSCode settings that conflict with VSCodeVim, then trace the extension's startup entry point. Add detection and a user-facing warning for those settings, and verify that startup behavior remains correct when the settings are present or absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100