microsoft / microsoft/language-server-protocol
Tags or categorys and filtration for references
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Coped from the issue: https://github.com/bmewburn/vscode-intelephense/issues/1813 @bmewburn
Feature description or problem with existing feature
Sometime I want to find only implementations/extensions of methods or only calls. Sometime I want to find all implementations and calls. The result doesn't split these categories.
Describe the solution you'd like
I would see marked categories of methods (an implementation, a call, an interface, if it is possible then an extension, uses, an initialization, declarations) or split calls, implementations, interfaces, etc. Also filtration of the result by these categories.
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 copied feature description and attached screenshots, then determine which reference categories and filtering behavior the protocol must standardize. Done requires an agreed scope and documented protocol design, since this issue names no files, tests, or implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100