mastofe

commit: 62677596077eb91d5818b0735b0aa952e7e4ef21
parent: bc39ad37c4b6372c98177f8c4fc525391c49f702
Author: Matt Jankowski <mjankowski@thoughtbot.com>
Date:   Thu, 25 May 2017 15:15:14 -0400

Disable the Rubocop Style/GuardClause cop (#3316)

There are many spots throughout the codebase which are showing as covered by
specs in the simplecov output -- but which are not actually run, because they
are on the same line as a guard clause.

I plan on fixing some of these issues, but don't want to keep triggering this
rubocop style violation.

My preference would be that we use the PR review process to identify places
where a guard clause might be appropriate, but that we leave this cop turned off
by default.
Diffstat:
M
.rubocop.yml
3
+++

1 file changed, 3 insertions(+), 0 deletions(-)
diff --git a/.rubocop.yml b/.rubocop.yml
@@ -74,6 +74,9 @@ Style/RegexpLiteral:
 Style/Lambda:
   Enabled: false
 
+Style/GuardClause:
+  Enabled: false
+
 Rails/HasAndBelongsToMany:
   Enabled: false