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
The basic idea is that we’ve catalogued all of the Rubocop offenses that haven’t been looked at in the rubocop_todo.yml file so that we can decide what we want to do with cops one by one.
If you want to tackle a cop, delete that section from the rubocop_todo.yml file, then run Rubocop to see what offenses associated with that cop need to be addressed.
Some of the cops should be discussed with @rylanb and @ericfreese to determine whether or not we even want to enforce them in the first place, and if so, whether or not we want to relax its configuration.
This issue will be closed when rubocop_todo.yml is empty or deleted.
The text was updated successfully, but these errors were encountered:
* regenerate rubocop_todo file to account for updates in inspected code
* Handle several rubocop syntax offenses and delete from rubocop_todo
* rebased with master and fix rubocop issue
* update each_key and each_value to single params
* fix conditional so it will not evaluate to nil
See PRs #85 and #93.
From @virtuallybing:
This issue will be closed when
rubocop_todo.yml
is empty or deleted.The text was updated successfully, but these errors were encountered: