Sha256: 5c710c1af66c3561fd7bcfa7dc31ca88369c864c49acdbf96619170d6d72c0ce

Contents?: true

Size: 1.49 KB

Versions: 5

Compression:

Stored size: 1.49 KB

Contents

inherit_from: .rubocop.todo.yml

################################################################################

AllCops:
  DisplayCopNames: true
  TargetRubyVersion: 2.4

## Metrics #####################################################################

Metrics/BlockLength:
  Exclude:
    - "Guardfile"
    - "spec/**/*"

## Styles ######################################################################

Style/AlignHash:
  EnforcedHashRocketStyle: table

Style/AlignParameters:
  EnforcedStyle: with_fixed_indentation

Style/BracesAroundHashParameters:
  Enabled: false

Style/Documentation:
  Enabled: false

Style/Encoding:
  EnforcedStyle: when_needed

Style/HashSyntax:
  EnforcedStyle: hash_rockets

Style/IndentArray:
  EnforcedStyle: consistent

Style/IndentHash:
  EnforcedStyle: consistent

# Follow your heart where it makes sense to use lambda or lambda literal.
# Enforcing it makes some pieces of code look REALLY terrible, e.g. in
# case of empty (noop) lambdas: `lambda { |_| }`.
Style/Lambda:
  Enabled: false

Style/MultilineMethodCallIndentation:
  EnforcedStyle: indented

# Enabling this cop makes Guardfile (which is full of pathname regexps)
# look absolutley style-inconsistent and terrible. In any case, this should
# be on developer's choice whenever to use `%r` or not. Just like we don't
# enforce to use `["foo"]` over `%w(foo)` and so on.
Style/RegexpLiteral:
  Enabled: false

Style/SpaceInLambdaLiteral:
  EnforcedStyle: require_space

Style/StringLiterals:
  EnforcedStyle: double_quotes

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
sidekiq-throttled-0.7.3 .rubocop.yml
sidekiq-throttled-0.7.2 .rubocop.yml
sidekiq-throttled-0.7.1 .rubocop.yml
sidekiq-throttled-0.7.0 .rubocop.yml
sidekiq-throttled-0.6.7 .rubocop.yml