Rails/HasManyOrHasOneDependent with paranoia gem

[rubocop]

Rails/HasManyOrHasOneDependent with paranoia gem

[ericboehs]

I also have this question. I think using a magic comment disable makes sense but I wish there was a better option. How better could RuboCop know to ignore this rule in this scenario?

[koic]

Currently RuboCop Rails does not have a configuration for option regarding combination with 3rd party gem. If you'd like to suppress the warn quickly , please make the following setting.

# Specify `dependet: nil`.
has_many :articles, dependent: nil

Further details: #467

or

# Your .rubocop.yml
Rails/HasManyOrHasOneDependent:
  Enabled: false

Thank you.

[gingerlime]

I bumped into this as well (similar scenario, not specific to the gem), but when I specify :dependent => nil I'm still getting a rubocop offense.

app/models/custom_quiz.rb:29:3: C: Rails/HasManyOrHasOneDependent: Specify a :dependent option.
  has_many :training_sessions, :dependent => nil
  ^^^^^^^^

[koic]

@gingerlime Is it happening in the latest RuboCop Rails 2.10? Can you provide the result of (bundle exec) rubocop -V?

[gingerlime]

# rubocop -V
0.93.1 (using Parser 3.0.1.1, rubocop-ast 1.5.0, running on ruby 2.6.5 x86_64-linux)
# cat Gemfile.lock |grep rubocop-rails
    rubocop-rails (2.9.1)

[koic]

The gems need to be updated and RuboCop Rails 2.10 requires RuboCop 1.7 or higher. Please bundle update rubocop rubocop-rails.
https://rubygems.org/gems/rubocop-rails/versions/2.10.1

[gingerlime]

Strange, but when I run bundle update rubocop rubocop-rails nothing changes... We're using pronto and pronto-haml seem to require rubocop < 1.0 so I guess that's the reason ... sorry about the false alarm. I will check with the pronto project and see if they can let us upgrade...