-
Notifications
You must be signed in to change notification settings - Fork 175
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
Hidden dependency on rubocop in ruby-lsp 0.18.2 #2604
Labels
Comments
thedanbob
added
bug
Something isn't working
help-wanted
Extra attention is needed
non-vscode
labels
Sep 23, 2024
Closed
Also seeing the same issue today! Proposed a very simple fix but there might be a more principled one. Happy to adopt a better solution :) |
Earlopain
added a commit
to Earlopain/ruby-lsp
that referenced
this issue
Sep 24, 2024
Closes Shopify#2604 Alternative to Shopify#2605 This moves the two command CI checks into the test suite. They would have cought this error, _expect_ rubocop is available to these. So, create a seperate Gemfile that contains only the gem itself.
Earlopain
added a commit
to Earlopain/ruby-lsp
that referenced
this issue
Sep 24, 2024
Closes Shopify#2604 Alternative to Shopify#2605 This moves the two command CI checks into the test suite. They would have cought this error, _expect_ rubocop is available to these. So, create a seperate Gemfile that contains only the gem itself. Co-authored-by: Theodore Liu <[email protected]>
Earlopain
added a commit
to Earlopain/ruby-lsp
that referenced
this issue
Sep 24, 2024
Closes Shopify#2604 Alternative to Shopify#2605 This moves the two command CI checks into the test suite. They would have cought this error, _expect_ rubocop is available to these. So, create a seperate Gemfile that contains only the gem itself. Co-authored-by: Theodore Liu <[email protected]>
Okay, we just released v0.18.3 with the fix. Here's how to force update: VS Code
Non VS Code
|
Earlopain
added a commit
to Earlopain/ruby-lsp
that referenced
this issue
Sep 24, 2024
The CI commands use the Gemfile of the repo, which contains additional gems like `rubocop` and `syntax_tree`. This hides issues like Shopify#2604. So, create a separate Gemfile containing only ruby-lsp and use that instead
vinistock
pushed a commit
that referenced
this issue
Sep 30, 2024
The CI commands use the Gemfile of the repo, which contains additional gems like `rubocop` and `syntax_tree`. This hides issues like #2604. So, create a separate Gemfile containing only ruby-lsp and use that instead
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Reproduction steps
Start Ruby LSP in a Rails project that isn't using Rubocop.
Error message
Workaround
Add
rubocop
to the Gemfile.I suspect the issue was introduced here: 5ed8b91
The text was updated successfully, but these errors were encountered: