Skip to content
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

Implementing workspace/configuration #1268

Closed
nangtrongvuon opened this issue Dec 14, 2021 · 1 comment · Fixed by #1684
Closed

Implementing workspace/configuration #1268

nangtrongvuon opened this issue Dec 14, 2021 · 1 comment · Fixed by #1684
Labels
A-language-server Area: Language server client C-enhancement Category: Improvements

Comments

@nangtrongvuon
Copy link

Some LSP servers such as the Dart LSP server requests settings with workspace/configuration. Currently there is no way to pass in such settings since helix does not support this yet.

Implementing workspace/configuration (and workspace/didChangeConfiguration) will allow more LSP settings and changing settings on the fly without restarting the server.

@nangtrongvuon nangtrongvuon added the C-enhancement Category: Improvements label Dec 14, 2021
@nangtrongvuon nangtrongvuon changed the title Implementing workspace/configuration Implementing workspace/configuration Dec 14, 2021
@kirawi kirawi added the A-language-server Area: Language server client label Dec 14, 2021
@hovsater
Copy link
Contributor

hovsater commented Jan 7, 2022

I stumbled across this as well while integrating the HTML language server with Helix. I managed to get the language server running, but I couldn't enable formatting as it expects me to set html.format.enable to true. All configuration is done through the Configuration Request.

For the HTML language server specifically, there's a lot of configuration available as can be seen here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-language-server Area: Language server client C-enhancement Category: Improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants