Explore tweets tagged as #Ruby_LSP
It took me a while to figure out how to debug Rails applications and RSpec tests in VS Code. Finally got it working using the great Ruby LSP extension. I summarized the steps in a blog post 👇🏻
3
4
67
My brain is a bit hurt by futures in @zeddotdev, but the pull diagnostic is somewhat here. This is just the basic stuff, and there's still a long road ahead. In this example, I am running Ruby LSP, and Zed pulls diagnostics from it.
2
4
47
Zed 에디터에서 Ruby LSP 설정 및 활용 가이드.Zed 에디터에서 공식 Ruby 확장 프로그램을 통해 Ruby LSP를 설정하고 활용하는 방법을 상세히 설명합니다. #ruby_lsp.
0
0
0
I know that a lot of people are really happy because of the LSP features in ruby_lsp, but I'd say that the awesome part is the DAP integration. That "Debug" code lens for tests saved me countless hours. Thank you @paracycle, @vinistock, @_st0012 & the rest of the ruby_lsp team!
1
5
21
Huge news for Ruby LSP users: `textDocument/diagnostic` aka pulling diagnostics is now available in the latest preview version of @zed (0.191.0)! Please give it a try! Don't forget to disable `rubocop`. Thanks to the @zeddotdev team for working and landing it!
1
2
15
Ruby LSP plugin v0.0.7 is now available for @rubymine. This release adds support for toggling code actions. I highly recommend updating and disabling "refactor.rewrite"(tmp solution) to avoid the message about an invalid location for placing the refactor for toggling block style.
0
0
2