[Fix #10648] Allow Style/TernaryParentheses
to take priority over Style/RedundantParentheses
for requiring parentheses
#10874
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Style/TernaryParentheses
allows RuboCop to require ternary conditions are wrapped in parentheses, but this behaviour doesn't take effect whenStyle/RedundantParentheses
is also enabled, in order to prevent an infinite loop.However, it makes more sense for
TernaryParentheses
to take priority here and haveRedudantParentheses
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:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).bundle exec rake default
. It executes all tests and runs RuboCop on its own code.{change_type}_{change_description}.md
if the new code introduces user-observable changes. See changelog entry format for details.