microsoft / microsoft/language-server-protocol
feat: One-way linked editing ranges
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Suppose for example a lsp server wanted to use linked editing ranges for more fluid renaming of local variables. It would make more sense for changes at the declaration/definition site to propagate to the usages, while changes at the usage sites do not rename the variables (the user probably just wanted to change that one usage to some other variables)
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
Review the linked editing ranges specification and the issue's declaration-versus-usage proposal first. Define how one-way propagation should be represented in the protocol and what behavior language servers and clients should observe when edits originate at each range.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100