pry--pry/.rubocop_todo.yml

# This configuration was generated by
# `rubocop --auto-gen-config`
# on 2019-03-21 00:51:00 +0200 using RuboCop version 0.66.0.
# The point is for the user to remove these configuration records
# one by one as the offenses are removed from the code base.
# Note that changes in the inspected code, or installation of new
# versions of RuboCop, may require this file to be generated again.

# Offense count: 88
Metrics/AbcSize:
  Max: 48

# Offense count: 191
# Configuration parameters: CountComments, ExcludedMethods.
# ExcludedMethods: refine
Metrics/BlockLength:
  Max: 794

# Offense count: 1
# Configuration parameters: CountBlocks.
Metrics/BlockNesting:
  Max: 4

# Offense count: 19
# Configuration parameters: CountComments.
Metrics/ClassLength:
  Max: 317

# Offense count: 32
Metrics/CyclomaticComplexity:
  Max: 32

# Offense count: 114
# Configuration parameters: CountComments, ExcludedMethods.
Metrics/MethodLength:
  Max: 101

# Offense count: 1
# Configuration parameters: CountKeywordArgs.
Metrics/ParameterLists:
  Max: 6

# Offense count: 29
Metrics/PerceivedComplexity:
  Max: 25
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`# This configuration was generated by`
			# `rubocop --auto-gen-config`
Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# on 2019-03-21 00:51:00 +0200 using RuboCop version 0.66.0.`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`# The point is for the user to remove these configuration records`
			`# one by one as the offenses are removed from the code base.`
			`# Note that changes in the inspected code, or installation of new`
			`# versions of RuboCop, may require this file to be generated again.`

Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# Offense count: 88`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`Metrics/AbcSize:`
Bump rubocop to v0.65.0 and generate config 2019-02-24 12:58:59 -05:00			`Max: 48`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00
Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# Offense count: 191`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`# Configuration parameters: CountComments, ExcludedMethods.`
			`# ExcludedMethods: refine`
			`Metrics/BlockLength:`
rubocop: fix offences of the Metrics/LineLength cop I realise that some code might be less readable now, but now that we set a good default limit, we protect the codebase from further mess. It's important to do this to prevent adding more mess to already messy code that we have. :doctor: 2019-03-03 10:37:58 -05:00			`Max: 794`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00
			`# Offense count: 1`
			`# Configuration parameters: CountBlocks.`
			`Metrics/BlockNesting:`
			`Max: 4`

Bump rubocop to v0.65.0 and generate config 2019-02-24 12:58:59 -05:00			`# Offense count: 19`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`# Configuration parameters: CountComments.`
			`Metrics/ClassLength:`
Rename '_pry_' to 'pry_instance' Although `_pry_` is a well-established name, it is confusing. `pry_instance` is a clearer name (arguably the best name). This change was dictated by Rubocop but I support it. Therefore, I decided to do it, but I realise it's a big change. `Pry::Command` deprecates `_pry_` and emits a warning. This seems to be the only place where `_pry_` is used publicly. Another place where it may affect the user is the sticky locals area. I don't think it will be a big issue there, though. 2019-03-22 18:44:56 -04:00			`Max: 317`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00
Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# Offense count: 32`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`Metrics/CyclomaticComplexity:`
			`Max: 32`

Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# Offense count: 114`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`# Configuration parameters: CountComments, ExcludedMethods.`
			`Metrics/MethodLength:`
Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`Max: 101`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00
			`# Offense count: 1`
			`# Configuration parameters: CountKeywordArgs.`
			`Metrics/ParameterLists:`
			`Max: 6`

Bump rubocop to v0.66.0 and update rubocop_todo 2019-03-20 18:51:57 -04:00			`# Offense count: 29`
rubocop: generate config The config ignores all violations for now. We will be fixing them at our own pace. 2018-10-06 07:40:35 -04:00			`Metrics/PerceivedComplexity:`
			`Max: 25`