RuboCop complains when using "Hash.new"

Question

RuboCop complains when I use Hash.new, and assumes that I use a hash literal instead. Is there a way to get RuboCop to ignore usage Hash.new? In particular, can I change the configuration .rubocop.ymlto allow use Hash.newwithout involving any complaints?

Answer 1

You can disable Rubocop::Cop::Style::EmptyLiteralin the rubocop.yml file:

# .rubocop.yml
Style:
  EmptyLiteral: false

Or, if you want to just ignore a specific line:

hsh = Hash.new # rubocop:disable Style/EmptyLiteral

Answer 2

Ruby Style Guide , . , , hash = {} hash = Hash.new.

, , , Style/EmptyLiteral cop, , .

rubocop.yml :

Style:
  EmptyLiteral: false

# rubocop:disable Style/EmptyLiteral
hash = Hash.new 
# rubocop:enable Style/EmptyLiteral

:

hash = Hash.new # rubocop:disable Style/EmptyLiteral

---

, Rubocop, .