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

Unmark AutoCorrect: false from Performance/StringInclude #263

Conversation

koic
Copy link
Member

@koic koic commented Oct 10, 2021

This AutoCorrect: false looks like it was set when there was no way to safe autocorrect by SafeAutocorrect: false.

Test code for the autocorrection exists. So it can be enabled by default. However, it is still unsafe because SafeAutocorrect: false.


Before submitting the PR make sure the following are checked:

  • 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.
  • 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.
  • The PR relates to only one subject with a clear title
    and description in grammatically correct, complete sentences.
  • Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

This `AutoCorrect: false` looks like it was set when there was no way
to safe autocorrect by `SafeAutocorrect: false`.

Test code for the autocorrection exists. So it can be enabled by default.
However, it is still unsafe because `SafeAutocorrect: false`.
@koic koic force-pushed the change_unmark_autocorrect_false_from_performance_string_include branch from 61e4d74 to 991a414 Compare October 10, 2021 11:20
@koic koic merged commit 41d3fd8 into rubocop:master Oct 30, 2021
@koic koic deleted the change_unmark_autocorrect_false_from_performance_string_include branch October 30, 2021 03:50
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.

None yet

1 participant