diff options
| author | Lin Jen-Shin <godfat@godfat.org> | 2017-02-13 20:37:04 +0800 |
|---|---|---|
| committer | Lin Jen-Shin <godfat@godfat.org> | 2017-02-14 00:10:39 +0800 |
| commit | 1f9c90b81462d0b34c2baa56993e233dfb4b6d01 (patch) | |
| tree | 6cfd471241bd79d3a2b07422217b4bc14b219512 | |
| parent | 79e8e6134f89c4a09a422ca128a7579d844f040c (diff) | |
| download | gitlab-ce-disable-rubocop-times-map.tar.gz | |
Disable Rubocop Performance/TimesMapdisable-rubocop-times-map
This cop would complain:
> C: Performance/TimesMap: Use Array.new with a block instead of .times.map.
I don't think this makes sense. What if we really want to have
sequential numbers? We could do: `0.upto(9).map` but how that's
so bad than using `10.times.map`? Performance doesn't really
matter here, we're certainly not running this in a loop. It's
generally used for generating some testing data only.
| -rw-r--r-- | .rubocop.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.rubocop.yml b/.rubocop.yml index d30846e6e0b..39b56e0f952 100644 --- a/.rubocop.yml +++ b/.rubocop.yml @@ -713,7 +713,7 @@ Performance/StringReplacement: # Checks for `.times.map` calls. Performance/TimesMap: - Enabled: true + Enabled: false # Rails ####################################################################### |