- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 13 Feb, 2017 1 commit
-
-
Robert Speicher authored
-
- 10 Feb, 2017 3 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
This is a little too picky, even for us.
-
- 09 Feb, 2017 1 commit
-
-
Robert Speicher authored
-
- 07 Feb, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 02 Feb, 2017 1 commit
-
-
Mike Greiling authored
-
- 11 Jan, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 10 Jan, 2017 1 commit
-
-
Mike Greiling authored
-
- 16 Dec, 2016 1 commit
-
-
Rydkin Maxim authored
-
- 20 Oct, 2016 1 commit
-
-
Adam Niedzielski authored
We have to use the lowest common denominator to check the supported syntax and in our case it is Ruby 2.1. Please note that it will not help with unsupported syntax in HAML files because they are not checked by Rubocop.
-
- 04 Oct, 2016 1 commit
-
-
Robert Speicher authored
`Style/VariableNumber` is explicitly disabled because I don't think we care if we name a variable `var_1` or `var1`.
-
- 03 Oct, 2016 1 commit
-
-
Robert Speicher authored
-
- 21 Sep, 2016 1 commit
-
-
Robert Speicher authored
This reverts commit cac2ecc53d8b, reversing changes made to d91b03970cf1.
-
- 15 Sep, 2016 1 commit
-
-
Robert Speicher authored
-
- 01 Sep, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 06 Aug, 2016 3 commits
-
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
- 03 Aug, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 20 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
Avoid multi-line ?: (the ternary operator). Use if/unless instead. See #17478
-
- 19 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
This enables following cops: Check for useless access modifiers Lint/UselessAccessModifier Checks for attempts to use `private` or `protected` to set the visibility of a class method, which does not work. Lint/IneffectiveAccessModifier This also disables two false possitives in concerns.
-
- 13 Jul, 2016 3 commits
-
-
Connor Shea authored
-
Connor Shea authored
-
-
- 08 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 01 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 30 Jun, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 29 Jun, 2016 3 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Yorick Peterse authored
There are currently two cops for this: * Migration/AddIndex: checks if indexes are added concurrently * Migration/ColumnWithDefault: checks if columns with default values are added in a concurrent manner Both cops are fairly simple and make no attempt at correcting the code as this is quite hard to do (e.g. modifications may need to be applied in various places in the same file). They however should provide enough to catch people ignoring the comments in generated migrations telling them to use add_concurrent_index or add_column_with_default.
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 429cd5e57fb1.
-
James Lopez authored
-
- 10 Jun, 2016 1 commit
-
-
Grzegorz Bizon authored
See #17478
-
- 09 Jun, 2016 1 commit
-
-
Sean McGivern authored
Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file.
-
- 04 Jun, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 03 Jun, 2016 1 commit
-
-
James Lopez authored
This reverts commit 7a0cd631f3f5.
-