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 #10136] Update Lint/AssignmentInCondition to not consider assignments within blocks in conditions #10137

Merged
merged 1 commit into from Sep 29, 2021

Conversation

dvandersluis
Copy link
Member

Assignments within a block are not relevant to this cop because they don't affect the same scope.

Fixes #10136.


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.

…er assignments within blocks in conditions.
@koic koic merged commit 6dfc273 into rubocop:master Sep 29, 2021
@koic
Copy link
Member

koic commented Sep 29, 2021

Thanks!

jonas054 added a commit to jonas054/rubocop that referenced this pull request Mar 23, 2024
In rubocop#10137 a fix was made that makes the condition

asgn_node.send_type? && !asgn_node.assignment_method?

unnecessary in AssignmentInCondition#skip_children?(). The spec example
'accepts = in a block followed by method call' that was added to regression
test this part of the code still passes if I remove the condition.
bbatsov pushed a commit that referenced this pull request Mar 25, 2024
In #10137 a fix was made that makes the condition

asgn_node.send_type? && !asgn_node.assignment_method?

unnecessary in AssignmentInCondition#skip_children?(). The spec example
'accepts = in a block followed by method call' that was added to regression
test this part of the code still passes if I remove the condition.
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.

Lint/AssignmentInCondition giving false positives in block-in-condition
2 participants