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 #719] Fix a false negative for Rails/FormattedS #720

Merged

Conversation

koic
Copy link
Member

@koic koic commented Jun 17, 2022

Fixes #719.

This PR fixes a false negative for Rails/FormattedS when using safe navigation operator.


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.
  • If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Fixes rubocop#719.

This PR fixes a false negative for `Rails/FormattedS`
when using safe navigation operator.
@koic koic merged commit 5f38b74 into rubocop:master Jun 19, 2022
@koic koic deleted the fix_a_false_negative_for_rails_to_formatted_s branch June 19, 2022 21:43
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.

False negative for Rails/FormattedS with safe navigation operator
1 participant