-
Notifications
You must be signed in to change notification settings - Fork 23
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
Razor/cshtml syntax support #17
Comments
Personally, I am not interested in implementing this. I would however of course accept a PR for this :) |
https://github.com/tris203/rzls.nvim/ may be of interest. Still in very early state ( see tris203/rzls.nvim#2 ) but I managed to get it to attach and provide some code actions. |
Looks kinda abandoned. I just discovered this tho. |
hi @Crashdummyy, did you have a chance to try cutlass.nvim to see if it works? |
sometime next week ( I am still on vacation and didn't bring my laptop with me ) |
Okay I either configured it somewhat wrong or its not really usable at this point. |
@Crashdummyy, it doesnt seem to be working from my end as well. Running |
You have to alter the hardcoded paths and compile the razor lsp to that location. |
@Crashdummyy I've found a problem in your fork cutlass in that it uses |
Yeah the fork is borked I need to remove it. |
Yea I realized after a while that it just behaves unusually due to it using some weird stuff with virtual buffers and it also attaching multiple lsps to the same buffer. I did have a look at the c# dev kit extension for vscode to see if it's not possible to reverse engineer how the lsp works there or something along those lines |
I started working on my fork of https://github.com/tris203/rzls.nvim. I was able to make the Razor LSP communicate with the Roslyn LSP and got hover working properly 😄. I'm trying to tackle completions now but it's been a challenge... |
@neubaner whoa!!! nicely done!!!! I'll check it out to see if I can get it to work as well. Right now without razor lsp, in my neovim i just set up my .razor markup file along with it's related code-behind .razor.cs file. Example:
The C# lsp works in the code-behind .razor.cs file. The last piece of the puzzle of perfect dotnet development neovim config is setting up razor lsp. Hopefully having a razor lsp work soon would greatly imporove the dotnet development experience in neovim. btw, @neubaner you can use https://github.com/jlcrochet/vim-razor for razor syntax highlighting. |
@neubaner How have you configured roslyn.nvim and rzls.nvim to get that to work? |
@jdrupal-dev Take a look at the README of https://github.com/tris203/rzls.nvim. @tris203 have a PR open to address this 😄. |
Thank you, I provided some details here: tris203/rzls.nvim#3 (comment) |
Support for razor files.
Going to try to get the ball rolling on this fork. See previous discussion..
As stated over there, roslyn should theoretically already support this.
The text was updated successfully, but these errors were encountered: