When I was working on #1226, I noticed that this gem still has the ruby-lsp as a development dependency.
We made changes so that the server can auto-update itself and it's no longer recommended to leave it in the gemspec or Gemfile.
This PR just removes the ruby-lsp from the gemspec so that people working on it get auto-updates. I also upgraded the parser gem because there's a bug that prevents the LSP from starting in older versions.
These are only development changes.
How has this been tested?
Opened VS Code on the project, verified that I got the latest Ruby LSP server version running.
Checklist:
[x] My commit message follow the pattern described in here
[x] I have performed a self-review of my own code.
[x] N/A I have added tests that prove my fix is effective or that my feature works.
Description
When I was working on #1226, I noticed that this gem still has the
ruby-lsp
as a development dependency.We made changes so that the server can auto-update itself and it's no longer recommended to leave it in the gemspec or Gemfile.
This PR just removes the
ruby-lsp
from the gemspec so that people working on it get auto-updates. I also upgraded theparser
gem because there's a bug that prevents the LSP from starting in older versions.These are only development changes.
How has this been tested?
Opened VS Code on the project, verified that I got the latest Ruby LSP server version running.
Checklist: