Microsoft/vscode
View on GitHubExtensions: "group" should provide intellisense to show valid groups to contribute menus to
Open
#42,475 opened on Jan 30, 2018
2 comments (2 comments)1 reaction (1 reaction)0 assignees (0 assignees)TypeScript74,848 stars (74,848 stars)10,221 forks (10,221 forks)batch import
feature-requesthelp wantedmenus
Description

/cc @jrieken
Contributor guide
- Tech stack
- typescript
- Domain
- developer experiencetooling
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- half day
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Knowledge of VS Code extension manifest structureUnderstanding of JSON intellisense in VS Code
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 45
- Research direction
- Examine the VS Code source code for extension contribution point schemas (likely in `src/vs/platform/extensions/common/` or `extensions/`). Look for how intellisense is provided for `contributes.menus` groups. The issue requests that the 'group' property provide completions from valid groups defined by other extensions or VS Code itself. Check existing schema definitions and completions providers. Consider using the extension manifest schema or providing a dynamic provider that reads registered groups from extensions. No linked PRs or maintainer comments to follow.