Prompt users to contribute with missing extensions and themes inside the editor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
We regularly see incoming requests for missing VS Code themes and extensions. The relevant existing docs[1] could be updated or take into account the relevant Open VSX docs[2] but the documentation could still remain hard to discover. See relevant discussion (internal). Cc @JohannesLandgraf @akosyakov
Proposal
In the meantime, we could introduce an extension to prompt users to contribute with missing extensions and themes inside the editor while searching for an extension or a theme.
Linking to some the relevant documentation could suffice.
| Early draft |
|---|
 |
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 implementation files or tests are identified. Start by reviewing the existing VS Code extensions documentation, the linked Open VSX publishing documentation, and the early draft; define the in-editor prompt and its documentation link, with completion meaning users can discover how to request missing extensions or themes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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