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
Upgrade Rubocop libraries #9201
Conversation
It appears that the upgrade itself has changed the standards or naming, revealing a lot of linting errors. @ahukkanen , @andreslucena please advise on the following:
|
I would vote for option 1, i.e. fixing the violations. I ran rubocop against the whole codebase with these changes and there were 1397 violations of which 997 were automatically corrected. So that leaves 400 violations to correct which is quite a "chore" but doable. We are not expecting you to do those changes unless you want to @alecslupu. We can also take this issue into the maintenance backlog. The current |
I can start working on this... |
Awesome, thanks for taking care of this one @alecslupu |
7f1c36d
to
fdca0a4
Compare
…e - should be RSpec/Capybara
… be RSpec/FactoryBot
@ahukkanen I have updated the PR to add a list of disabled cops to help us through upgrade. I would not want to make this PR a 100+ files changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me this approach seems perfectly fine.
Just one thing I did not completely understand so if you could explain @alecslupu I'd appreciate that.
@andreslucena Are you fine with the suggested approach fixing these issues?
🎩 What? Why?
Upgrade