Contents

inherit_from:
  - .rubocop_todo.yml

require:
  - rubocop-rspec

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

AllCops:
  DisplayCopNames: true
  TargetRubyVersion: 2.3
  Exclude:
    - "gemfiles/*"

## Layout ######################################################################

Layout/AlignHash:
  EnforcedHashRocketStyle: table

Layout/AlignParameters:
  EnforcedStyle: with_fixed_indentation

Layout/IndentArray:
  EnforcedStyle: consistent

Layout/IndentHash:
  EnforcedStyle: consistent

Layout/MultilineMethodCallIndentation:
  EnforcedStyle: indented

Layout/SpaceInLambdaLiteral:
  EnforcedStyle: require_space

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

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

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

Style/BracesAroundHashParameters:
  Enabled: false

Style/Documentation:
  Enabled: false

Style/HashSyntax:
  EnforcedStyle: hash_rockets

# 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

# 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/RescueStandardError:
  EnforcedStyle: implicit

Style/StringLiterals:
  EnforcedStyle: double_quotes

# I prefer Yoda style instead, but there's no such enforcement style.
Style/YodaCondition:
  Enabled: false

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
sidekiq-throttled-0.10.0.beta	.rubocop.yml
sidekiq-throttled-0.10.0.alpha	.rubocop.yml
sidekiq-throttled-0.9.0	.rubocop.yml