microsoft / microsoft/vscode-makefile-tools
Cleanup of stale launch configurations
Open
Nobody has claimed this yet.
enhancement
Feature: launch
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Launch configurations add up in time and pollute .vscode/settings.json, especially when exploring more launch targets with various debugging settings.
Think of a way to identify when they become stale. Find the best way to cleanup (with or without user interaction, ...etc...).
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 .vscode/settings.json and the launch-configuration behavior described in the issue. Define how stale configurations should be identified and whether cleanup is automatic or user-confirmed. Done means the cleanup approach is specified and implemented without allowing active launch targets to be removed unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100