Closed ta3pks closed 3 years ago
options are supposed to be specified as nested maps one key at a time I guess this has nothing to do with LanguageClient-neovim afterall
I think the issue you are/were having is that the rust-analyzer.
prefix on your options should not be included in this config section. The idea behind that not being necessary was that it was already clear that the initialization options were for rust-analyzer
(or whatever server you were configuring), but maybe that's not clear or correct enough and it's worth changing it to require the full option name.
Essentially, what you want to have there is something like this instead:
...
"initializationOptions": {
"procMacro.enable": v:true,
"cargo.loadOutDirsFromCheck": v:true,
},
...
@martskins that doesnt work either
"initializatinonOptions":{
"procMacro":{
"enable":v:true
}
}
dos work however
bin/languageclient --version
to get its version number.languageclient 0.1.161
:checkhealth LanguageClient
? :heavy_check_mark:Describe the bug
Initialization options described in rust analyzer manual has no effect on the language client. I enabled procmacros but still i get proc macro errors I also cannot seem to disable those diagnostics for the same reason usage of the options are clearly documented so either LanguageClient-neovim uses non-standard way of defining things or simply this is not implemented
Environment
nvim --version
orvim --version
):NVIM v0.4.4
git rev-parse --short HEAD
):next branch
bin/languageclient --version
):languageclient 0.1.161
Not relevant
rust-analyzer 60c501f
To Reproduce
Steps to reproduce the behavior: