rust-lang / rust-lang/rust-analyzer
LSP Config should be by feature
Open
Nobody has claimed this yet.
A-config
E-medium
S-actionable
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
To truly be compliant and for #144 we should probably split out the configuration by feature.
For instance in:
pub struct ClientCapsConfig {
pub location_link: bool,
// ...
}
location_link support can be different for goto definition vs goto type definition.
Contributor guide
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 locating the ClientCapsConfig definition and the code paths that consume its location_link setting. Review how goto definition and goto type definition capabilities are configured, then determine the feature-specific configuration boundaries. Done means the configuration can express different location_link support for those features and the relevant behavior remains compliant.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100