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 #12571] Fix false posives for Naming/BlockForwarding #12577

Merged

Conversation

koic
Copy link
Member

@koic koic commented Dec 28, 2023

Fixes #12571.

This PR fixes false positives for Naming/BlockForwarding when using explicit block forwarding in block method.


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • 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.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • 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.

Fixes rubocop#12571.

This PR fixes false positives for `Naming/BlockForwarding`
when using explicit block forwarding in block method.
@bbatsov bbatsov merged commit 91f7d9a into rubocop:master Jan 11, 2024
29 checks passed
@bbatsov
Copy link
Collaborator

bbatsov commented Jan 11, 2024

Looks good to me. Thanks!

@koic koic deleted the fix_false_positives_for_naming_block_forwarding branch January 11, 2024 07:04
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.

Naming/BlockForwarding with anonymous block parameter (Ruby 3.3.0)
2 participants