This repository was archived by the owner on Aug 14, 2024. It is now read-only.
Upgrade rubocop-performance to version 1.14.3 #107
Closed
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop-performance (~> 1.7.0 → ~> 1.14.3) · Repo · Changelog
Release Notes
1.14.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Cut 1.14.3Update ChangelogMerge pull request #296 from koic/fix_a_false_negative_for_performance_string_identifier_argumentFix a false negative for `Performance/StringIdentifierArgument`Suppress `Lint/NonAtomicFileOperation` offenseSuppress RuboCop offensesMerge pull request #295 from ydah/change_suggest_rake_task_warningChange command for the rake task with arguments to a style that can also be used in zshMerge pull request #294 from koic/fix_false_negative_for_performance_chain_array_allocationAdd settings to `Naming/InclusiveLanguage`Fix a false negative for `Performance/ChainArrayAllocation`Merge pull request #293 from ydah/fix_spellingFix a typoSwitch back docs version to masterDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands