This repository was archived by the owner on Aug 14, 2024. It is now read-only.
Upgrade rubocop-performance to version 1.13.0 #91
Conversation
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
|
Code Climate has analyzed commit cc8d042 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 98.8% (0.0% change). View more on Code Climate. |
Contributor
Author
|
Closed in favor of #92. |
Contributor
Author
|
Closed in favor of #92. |
1 similar comment
Contributor
Author
|
Closed in favor of #92. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.13.0) · Repo · Changelog
Release Notes
1.13.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Cut 1.13.0Update ChangelogRemove redundant config from .rubocop.ymlMerge pull request #276 from koic/new_add_new_performance_string_identifier_argument_copAllow for Gemfile.localMerge pull request #277 from koic/fix_incorrect_autocorrect_for_performance_map_compactRemove a redundant unsafe descriptionFix an incorrect autocorrect for `Performance/MapCompact`Add new `Performance/StringIdentifierArgument` copUse `<<next>>` instead of the next version when running `rake new_cop`Support `VersionAdded: '<<next>>'` for project_spec.rbAdd the changelog entry for #275Tweak the PR templateRemove an obsolete development taskMerge pull request #275 from koic/change_unmark_autocorrect_false_from_performance_times_mapMerge pull request #274 from koic/change_unmark_autocorrect_false_from_performance_case_when_splatChange from `AutoCorrect: false` to `SafeAutoCorrect: false` for `Performance/TimesMap`Change from `AutoCorrect: false` to `SafeAutoCorrect: false` for `Performance/CaseWhenSplat`Add examples for `IncludeActiveSupportAliases` option of `Performance/DoubleStartEndWith` copHave `cut_release` handle "config/default" and generate cops docMerge pull request #273 from koic/fix_incorrect_autocorrect_for_performance_redundant_string_charsFix an incorrect autocorrect for `Performance/RedundantStringChars`Merge pull request #269 from leoarnold/leoarnold/to_dMerge pull request #270 from leoarnold/leoarnold/sum-docMark `Performance/Sum` auto-correction as unsafe and extend documentationAdd #to_d support to BigDecimalWithNumericArgumentMerge pull request #271 from leoarnold/leoarnold/fix-204[Fix #204] Add `Performance/Sum` option to ignore potential false positivesMerge pull request #268 from dvandersluis/gemspec/require-mfaSet `rubygems_mfa_required` in gemspec.Add a spec for the changelog file formatBump RuboCop RSpec to 2.5Switch 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