rust-lang / rust-lang/rust-analyzer

Surface information for tags to CallHierarchyItem and workspace symbol

Open
#5,493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-lsp C-enhancement S-actionable
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

There are a few fields we can't fill out for call hierarchy and workspace symbols since they only traffic in NavigationTarget

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how NavigationTarget is used for call hierarchy and workspace symbols, then compare its available information with the fields required by CallHierarchyItem and workspace symbol responses. The work is done when the relevant tag information can be surfaced in both response types without relying only on NavigationTarget.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.