Fix false positives in Rails/StrongParametersExpect#1616
Merged
koic merged 1 commit intoMay 13, 2026
Merged
Conversation
This PR fixes false positives in `Rails/StrongParametersExpect` when `params[:key]` is followed by a nil-safe conversion method such as `to_i`, `to_s`, `to_a`, `to_f`, or `to_h`. These methods are defined on `NilClass` and return a sensible default (e.g., `nil.to_i` returns `0`) without raising, so the caller is intentionally treating the parameter as optional. This is the same rationale behind the existing `PRESENCE_CHECK_METHODS` allow list (`nil?`, `blank?`, `present?`, `presence`).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 fixes false positives in
Rails/StrongParametersExpectwhenparams[:key]is followed by a nil-safe conversion method such asto_i,to_s,to_a,to_f, orto_h.These methods are defined on
NilClassand return a sensible default (e.g.,nil.to_ireturns0) without raising, so the caller is intentionally treating the parameter as optional. This is the same rationale behind the existingPRESENCE_CHECK_METHODSallow list (nil?,blank?,present?,presence).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.