Skip to content

LSP Config should be by feature #4404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kjeremy opened this issue May 9, 2020 · 1 comment
Open

LSP Config should be by feature #4404

kjeremy opened this issue May 9, 2020 · 1 comment
Labels
A-config configuration E-medium S-actionable Someone could pick this issue up and work on it right now

Comments

@kjeremy
Copy link
Contributor

kjeremy commented May 9, 2020

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.

@matklad
Copy link
Member

matklad commented May 11, 2020

Yeah.... This is E-annoying at its finest

@lnicola lnicola added the S-actionable Someone could pick this issue up and work on it right now label Jan 22, 2021
@Veykril Veykril added the A-config configuration label Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-config configuration E-medium S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Development

No branches or pull requests

4 participants