microsoft / microsoft/language-server-protocol
Support late resolution of symbol (reference) information
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
It would be nice if a location and a container of symbol are resolved later. In our case we have an index of symbols but it is missing information about locations, so to compute them we have to load models for all found symbols. I assume that locations are required for navigation and their can be computed on demand later. The same should be true for references.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the language-server protocol definitions related to symbol locations, containers, and references. Determine how late resolution could be represented and how navigation clients would request it. Done means the protocol behavior, compatibility implications, and affected symbol/reference information are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100