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 (1,283 forks)batch import
feature-requesthelp wantedtypescript

Repository metrics

Stars
 (14,836 stars)
PR merge metrics
 (Avg merge 6h 26m) (15 merged PRs in 30d)

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

Research direction
Examine standaloneLanguages.ts to understand the pattern for registering providers (e.g., registerCompletionItemProvider, registerCodeActionProvider). Then implement registerCallHierarchyProvider following the same pattern, adding a function in standaloneLanguages.ts and exporting it. Ensure the call hierarchy provider is registered with the existing internal service.
Tech stack
typescriptjavascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Clear
Prerequisites
TypeScriptMonaco editor internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75