Microsoft/monaco-editor

[Feature Request] Add registerCallHierarchyProvider to standalone monaco exports

Open

#3,442 opened on Nov 30, 2022

View on GitHub
 (6 comments) (0 reactions) (1 assignee)JavaScript (14,836 stars) (1,283 forks)batch import
feature-requesthelp wantedtypescript

Description

Context

  • This issue is not a bug report. (please use a different template for reporting a bug)
  • This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description

There is existing infrastructure in VS Code for a CallHierarchyProvider, which the TypeScript extension makes use of (as a VS Code Extension API). But, it looks like the required glue code hasn't been added to the standalone Monaco API.

It could be as simple as a few lines of code in src/vs/editor/standalone/browser/standaloneLanguages.ts to add a stub to receive the provider and register it with the existing service.

(There appear to be a couple more registerX() methods in the vscode extension API as well, which haven't been added to Monaco. I don't know what they do, but maybe it's worth adding them all, to bring standaloneLanguages.ts fully up-to-date.)

Contributor guide

Tech stack
javascripttypescript
Domain
developer experiencetoolingfrontend
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
TypeScriptMonaco Editor codebase structureVS Code extension API concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The main file to modify is `src/vs/editor/standalone/browser/standaloneLanguages.ts`. Study existing `registerXxxProvider` methods to understand the pattern (e.g., `registerCompletionItemProvider`, `registerHoverProvider`). The issue suggests adding `registerCallHierarchyProvider` and possibly other missing methods by mirroring the VS Code API. Check the existing service interfaces for call hierarchy in the codebase (likely in `vs/editor/common/language`). Ensure the provider is properly wired to the existing infrastructure, similar to other providers. The issue comments may contain further guidance; review them before starting.