microsoft / microsoft/language-server-protocol
Clarify whether $0 can be a placeholder (${0:foo})
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Please reopen this issue.
The current definition is very vague, with the following 4 scenarios:
- $0 as the final endpoint (implemented in Neovim)
- ${0:placeholder} as the final endpoint
- $0 as the starting point
- ${0:placeholder} as the starting point (implemented in Dart LSP).
Although the other two scenarios have not been encountered in my practice, they still comply with the protocol. Using Dart on Neovim is very frustrating for me. Due to the overly broad protocol definition, I am not even sure if this issue should be addressed by Dart or Neovim.
If you close this issue without any reply, I will assume that you acknowledge the 4 scenarios, and I can use this issue as reference to report to Neovim. Otherwise, please provide a clear definition before closing this issue.
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 reading linked issue #1946 and the current protocol definition, then compare it with the four placeholder and endpoint scenarios listed here. Done means publishing a clear, unambiguous definition of whether each scenario is valid and identifying whether the protocol or an implementation needs clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, neovim
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100