microsoft / microsoft/language-server-protocol
Support looking up types by (approximate) name instead of just position
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Through discussion here I learned that the protocol doesn't support looking up things by name. Previously using tagging programs it was quite easy for me to fuzzy search for a class name in my code base. Now if I want to look at the definition of something even if I know its exact name I have to insert a reference to it into my current source file in order to be able to look it up. Ideally you could query a name and get back a list of possibilities, enabling editors to have features like narrowing down what class you mean as you type.
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 with the issue description and the linked Emacs Stack Exchange discussion to understand the requested name-based lookup workflow. Define what the language server protocol would need to specify for approximate-name queries and lists of possible results; done means the protocol change and its expected responses are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100