microsoft / microsoft/language-server-protocol
Call hierarchies, more info needed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
When I read the 3.16 information about call hierarchies, I am left scratching my head. Is this mechanism all about finding out who calls or is called by a symbol (the cursor is placed on)?
The first question that pops up is how would this work in a functional language where a caller or callee is a piece of runtime data?
Second question is, given a cursor on the middle of the "print" call reference of the proverbial hello world program, what should the various call hierarchy requests do?
Might be very useful to provide examples or cite references to further explain what the LSP designers are trying to accomplish/achieve with this mechanism.
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 LSP 3.16 call hierarchy section referenced in the issue and review its existing description. Add examples or references that clarify caller and callee behavior, including the hello-world print-call case and functional-language considerations; done means the mechanism and request behavior are understandable from the documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100