How to configure Blazor support for dotnet with rzls.nvim plugin #1864
Unanswered
andresparrab
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I have looked and looked and found this plugin so that i can work with blazor in nvim. but i don't know how to integrate this in lazyVim as everything just works. like the omnisharp extra everything is configure to work and it really works so well. that i don't use vs code, vs or rider, before i use all 3 because in some can do something that the other cannot but nvim can do everything....
Except Blazor before that is why stil use rider. but if i could get help ti integrate this plugin that has lps telescope and everything i would really be thankful.
https://github.com/tris203/rzls.nvim?tab=readme-ov-file
from the Readme file:
It can be included in your config:
Dependencies
You must install the following plugins:
Caution
Please see Integration section for extra arguments that must be passed to
roslyn.nvim setup.
The
html-lsp
is also required to provide completions and formatting. You caninstall and configure it via
mason
andnvim-lspconfig
.Integration
You can pass a configuration table to the
setup
function. The configuration options are:on_attach
: A function that is called when the LSP client attaches to a buffer.capabilities
: A table that defines the capabilities of the LSP client.path
: The path to the rzls executable if not installed via mason. If youhave installed via mason you can omit this option.
You also must configure the
roslyn.nvim
pluginto communicate with the razor LSP. To do so, you must pass the handlers defined in the
rzls.roslyn_handlers
module:Inlay Hints
Inlay hints are provided in razor documents via the roslyn lsp.
To enable, you must enable inlay hinting in nvim config
:h vim.lsp.inlay_hint.enable()
and also configure
csharp|inlay_hint_*
options in roslyn.nvimAdditional Configuration
Telescope
If you use telescope for definitions and references then you may want to add
additional filtering exclude references in the generated virtual files
Trouble
If you use trouble for diagnostics, then you want to excludion the virtual
buffers from diagnostics
Beta Was this translation helpful? Give feedback.
All reactions