Unify and improve code paths for Workspace Symbol and Document Symbol
Open
Nobody has claimed this yet.
area: language server
enhancement
- Dominant language
- Rust
- Stars
- 337
- Forks
- 32
- Avg merge
- 8d 17h
- Merged PRs (30d)
- 11
Description
Connected to https://github.com/posit-dev/positron/issues/3822
See https://github.com/posit-dev/ark/pull/571 and in particular https://github.com/posit-dev/ark/pull/571#discussion_r1797344751
- We use the indexer for workspace symbols, but not for document symbols. We should try and share more infrastructure here. Note that the indexer currently produces a flat list of symbols, but for outlines it is quite useful to have a nested list of symbols instead.
- We should produce nested "sections", particularly in the Document Symbol response, where it shows up in the Outline view. This would allow
## second ----to be a child of# first ----, and would also nest any functions / variables inside these section headers too.
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
Start by comparing the existing workspace-symbol and document-symbol paths, then read posit-dev/ark#571 and its discussion for the indexer context. Done means shared infrastructure where practical and nested document symbols, including section, function, and variable relationships in the Outline response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100