-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix rubocop config to remove error messages #8526
Conversation
BracesAroundHashParameters has been removed due to updated standards for ruby. More info found at: rubocop/rubocop#7641
Changed obselete rubocop configs to the configs superseeding them.
The old way was not recognised by rubocop, so changed to the new way with, as far as I can tell, the same function.
The previous fix introduced a warning, which is removed by this update.
In accordance with recomendations from rubocop
Thanks for opening this pull request! This space is protected by our Code of Conduct - and we're here to help. |
Code Climate has analyzed commit 31cb581 and detected 37 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
Codecov Report
@@ Coverage Diff @@
## main #8526 +/- ##
==========================================
- Coverage 82.01% 81.79% -0.22%
==========================================
Files 101 101
Lines 5899 5894 -5
==========================================
- Hits 4838 4821 -17
- Misses 1061 1073 +12
|
Hi, i'm so sorry to have missed this. I really appreciate it. I'm not completely sure what each change does, and I don't want to have to ask you to explain every line, but could you offer us an overview of what changes you made and how you approached them? Thank you! |
Hi, No worries, the changes was performed by stepping through the output of the linter, and changing the lines to follow the styleguide. As you say this was a long time ago and I sadly do not remember the exact logic behind each of the changes more than I documented in the individual commits. I might get back to this one day, but for the time being I do not have the time so I recommend closing the pull-request for now and giving somebody else the possibility to take a look at the issue. |
Thank you for your contribution! I'll do that, and apologies again! |
One step in fixing #6340
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
rake test
@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Hopefully I did things correct with this PR, if not please let me know so I can learn.