Skip to content
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

[Fix #103] Fix a false positive for Rails/FindEach #464

Merged
merged 1 commit into from
Apr 26, 2021

Conversation

koic
Copy link
Member

@koic koic commented Apr 26, 2021

Fixes #103.

This PR fixes a false positive for Rails/FindEach when not inheriting ActiveRecord::Base and using all.each.


Before submitting the PR make sure the following are checked:

  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
  • The PR relates to only one subject with a clear title
    and description in grammatically correct, complete sentences.
  • Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.
  • If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Fixes rubocop#103.

This PR fixes a false positive for `Rails/FindEach`
when not inheriting `ActiveRecord::Base` and using `all.each`.
@koic koic merged commit 8151200 into rubocop:master Apr 26, 2021
@koic koic deleted the fix_false_positive_for_rails_find_each branch April 26, 2021 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rails/FindEach reports issue on any class
1 participant