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 #535] Fix an error for Rails/HasManyOrHasOneDependent #536

Merged

Conversation

koic
Copy link
Member

@koic koic commented Sep 9, 2021

Fixes #535.

This PR fixes an error for Rails/HasManyOrHasOneDependent when using lambda argument and not specifying any options.


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 (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
  • 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#535.

This PR fixes an error for `Rails/HasManyOrHasOneDependent`
when using lambda argument and not specifying any options.
@koic koic merged commit 554f200 into rubocop:master Sep 9, 2021
@koic koic deleted the fix_error_for_rails_has_many_or_has_one_dependent branch September 9, 2021 16:01
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.

"An error occurred while Rails/HasManyOrHasOneDependent cop" since v2.12.0
1 participant