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 #10648] Allow Style/TernaryParentheses to take priority over Style/RedundantParentheses for requiring parentheses #10874

Merged
merged 1 commit into from Aug 6, 2022

Conversation

dvandersluis
Copy link
Member

@dvandersluis dvandersluis commented Aug 5, 2022

Style/TernaryParentheses allows RuboCop to require ternary conditions are wrapped in parentheses, but this behaviour doesn't take effect when Style/RedundantParentheses is also enabled, in order to prevent an infinite loop.

However, it makes more sense for TernaryParentheses to take priority here and have RedudantParentheses allow the parentheses instead of creating an infinite autocorrection loop.

This change moves the infinite loop protection into RedundantParentheses instead.


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.

… over `Style/RedundantParentheses`.

`Style/TernaryParentheses` allows RuboCop to require ternary conditions are wrapped in parentheses, but this behaviour doesn't take effect when `Style/RedundantParentheses` is also enabled, in order to prevent an infinite loop.

However, it makes more sense for `TernaryParentheses` to take priority here and have `RedudantParentheses` allow the parentheses instead of creating an infinite autocorrection loop.

This change moves the infinite loop protection into `RedundantParentheses` instead.
@bbatsov
Copy link
Collaborator

bbatsov commented Aug 6, 2022

Looks good to me. Thanks!

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.

Allow Style/TernaryParentheses to override Style/RedundantParentheses when parentheses are required
2 participants