[Fix #11182] Fix an incorrect autocorrect for Style/IfUnlessModifier
with Style/HashSyntax
#11185
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.
This PR intentionally separates two commits to resolve #11182.
First, this resolution of #11182 requires a change of
Style/HashSyntax
behavior.The first change makes
Style/HashSyntax
aware of without parentheses call expr follows. It prepares to preventStyle/HashSyntax
withStyle/IfUnlessModifier
autocorrection conflicts that resolve #11182.Before
Previously
Style/HashSyntax
accepted the following syntax to prevent syntax errors:This avoids the following incompatible syntax:
After
Style/HashSyntax
registers an offense for:And the autocorrection adds parentheses to prevent syntax errors shown in the URL:
https://bugs.ruby-lang.org/issues/18396
By assuming the above first change of
Style/HashSyntax
, the next commit fixes an incorrect autocorrect forEnforcedShorthandSyntax: always
ofStyle/HashSyntax
withStyle/IfUnlessModifier
when using Ruby 3.1.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.