[Fix #14441] Better hash access handling in Style/SafeNavigation
#14450
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
koic
reviewed
Aug 16, 2025
changelog/fix_fix_14441_better_hash_access_handling_in_20250815010135.md
Outdated
Show resolved
Hide resolved
…ion` - Make the `matching_call_nodes?` method account for differences in arguments. - Code like `foo[:bar] && foo[:baz].blank?` does not need safe navigation because the hash keys are different.
issyl0
force-pushed
the
fix-14441-safe-navigation-with-hash-access
branch
from
b43b25e to
7a08e3d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
matching_call_nodes?method account for differences in arguments.foo[:bar] && foo[:baz].blank?does not need safe navigation because the hash keys are different.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}.mdif the new code introduces user-observable changes. See changelog entry format for details.