microsoft / microsoft/language-server-protocol
Specify read-only locations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
It would be nice to provide a hint that locations (Location, LocationLink) could be read-only. For instance: if performing a find usages or a go to definition on a symbol that ends up in a third party library (crates, npm packages, disassembled .NET DLLs) you may not want that source to be editable at that location and could open up a document in read-only mode.
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 the linked rust-analyzer issue 6623 and the protocol definitions for Location and LocationLink. Determine how a read-only hint should be represented and how it would affect clients opening third-party or disassembled sources. Done means the protocol change is specified clearly enough for language servers and clients to implement consistently.
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
- 25/100