Mark Performance/Sum
auto-correction as unsafe and extend documentation
#270
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.
The documentaion of
Performance/Sum
talked about settingSafeAutoCorrect: true
for the cop, but Rubocop complained:so we add the
SafeAutoCorrect
option to the cop's defaultsand thereby mark it as (partially) unsafe.
This is NOT a change in behavior: The cop will still perform all
safe auto-corrections when using
-a
, and also (by default)perform all unsafe auto-corrections when using
-A
.Furthermore we extend the documentation in order to make it even more
clear in which cases auto-correction is unsafe, and why.
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).{change_type}_{change_description}.md
if the new code introduces user-observable changes. See changelog entry format for details.and description in grammatically correct, complete sentences.
bundle exec rake default
. It executes all tests and RuboCop for itself, and generates the documentation.