Problem
There is no way to disable individual language server features via yang.settings. Users may want to turn off specific features for performance reasons or to avoid conflicts with other tooling.
Proposal
Add on/off toggle settings for all implemented LSP features:
| Setting |
Controls |
Default |
code-lenses |
Code lens references |
on |
semantic-tokens |
Semantic token highlighting |
on |
validation |
Validation diagnostics |
on |
formatting |
Document formatting |
on |
code-actions |
Code actions (quick fixes) |
on |
completion |
Auto-completion |
on |
hover |
Hover information |
on |
definition |
Go to definition |
on |
references |
Find references |
on |
document-symbols |
Document symbols (outline) |
on |
document-highlight |
Highlight occurrences |
on |
rename |
Symbol renaming |
on |
Example yang.settings:
{
"semantic-tokens": "off",
"code-lenses": "off",
"validation": "on"
}Note: code-lenses already exists (as code-lenses in code, but code-lens-enabled in the settings schema). The schema should be fixed to match the actual preference key code-lenses.
Problem
There is no way to disable individual language server features via
yang.settings. Users may want to turn off specific features for performance reasons or to avoid conflicts with other tooling.Proposal
Add
on/offtoggle settings for all implemented LSP features:code-lensesonsemantic-tokensonvalidationonformattingoncode-actionsoncompletiononhoverondefinitiononreferencesondocument-symbolsondocument-highlightonrenameonExample
yang.settings:{ "semantic-tokens": "off", "code-lenses": "off", "validation": "on" }Note:
code-lensesalready exists (ascode-lensesin code, butcode-lens-enabledin the settings schema). The schema should be fixed to match the actual preference keycode-lenses.