-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails/HasManyOrHasOneDependent
reports false positive when has_many or has_one is called on an explicit receiver
#1158
Comments
samrjenkins
added a commit
to samrjenkins/rubocop-rails
that referenced
this issue
Oct 17, 2023
…e when has_many or has_one called on explicit receiver
samrjenkins
added a commit
to samrjenkins/rubocop-rails
that referenced
this issue
Oct 17, 2023
…ive when has_many or has_one called on explicit receiver
9 tasks
samrjenkins
added a commit
to samrjenkins/rubocop-rails
that referenced
this issue
Oct 17, 2023
…ive when has_many or has_one called on explicit receiver
samrjenkins
added a commit
to samrjenkins/rubocop-rails
that referenced
this issue
Oct 17, 2023
…ive when has_many or has_one called on explicit receiver
koic
added a commit
that referenced
this issue
Oct 18, 2023
…endent-false-positive [Fix #1158] Rails/HasManyOrHasOneDependent reports false positive when has_many or has_one called on explicit receiver
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rails/HasManyOrHasOneDependent
is reporting false positives when has_many or has_one is called on an explicit receiver. The pattern used to match awith_options
block does not match blocks which define a parameter:it will only match blocks without parameters:
Expected behavior
No offense:
Actual behavior
Two offenses:
Steps to reproduce the problem
See "Actual behaviour" example above
RuboCop version
The text was updated successfully, but these errors were encountered: