You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace all the Rubocop references within the namespace RubyLsp using the top-level namespace operand :: That's already the case on some instructions but not everywhere.
So basically RuboCop::Cop should be replaced by ::RuboCop::Cop. I will try to provide a PR.
The text was updated successfully, but these errors were encountered:
abrisse
added
bug
Something isn't working
vscode
This pull request should be included in the VS Code extension's release notes
labels
Jan 10, 2025
abrisse
added a commit
to PerfectMemory/ruby-lsp
that referenced
this issue
Jan 10, 2025
Thank you for the issue and the PR, but I'm not 100% sure that this is all that's needed to fix the conflicts.
I wrote here a bit about the issues that may happen with RuboCop pushing an add-on that conflicts with our internal implementation rubocop/rubocop#13628 (comment).
We will need a bit more coordination to make this transition work smoothly.
Description
Ruby LSP Information
The version 1.17.0 of the gem
rubocop
defines a new module RubyLsp::Rubocop. (link) that breaks several lines of code of the gemruby-lsp
.Reproduction steps
In my Gemfile.lock:
Fix
Replace all the
Rubocop
references within the namespaceRubyLsp
using the top-level namespace operand::
That's already the case on some instructions but not everywhere.So basically
RuboCop::Cop
should be replaced by::RuboCop::Cop
. I will try to provide a PR.The text was updated successfully, but these errors were encountered: