Upgrade rubocop to version 1.50.2 #44
Merged
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 (1.49.0 → 1.50.2) · Repo · Changelog
Release Notes
1.50.2
1.50.1
1.50.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 46 commits:
Cut 1.50.2Update Changelog[Fix #11803] Update the doc for `Style/RedundantFetchBlock`Merge pull request #11799 from koic/fix_a_false_positive_for_style_collection_compactMerge pull request #11805 from tagliala/chore/fix-typo-in-deprecated-attribute-assignment-copFix typo in DeprecatedAttributeAssignment cop[Fix #11800] Mark `Style/InvertibleUnlessCondition` as unsafeFix a false positive for `Style/CollectionCompact`[Doc] Tweak examples for `AllowMultilineFinalElement`[Fix #11792] Fix an error for `Lint/DuplicateMatchPattern`Switch back the docs versionCut 1.50.1Update Changelog[Docs] Remove a redundant blank line[Fix #11787] Fix a false positive for `Lint/DuplicateMatchPattern`Fix false negatives for `Style/ParallelAssignment`Add spec for `Style/RescueModifier`[Fix #11783] Fix a false positive for `Style/RedundantLineContinuation`Switch back the docs versionCut 1.50Update ChangelogMake `Lint/RedundantStringCoercion` aware of print method argumentsAdd specs for redundant `SafeAutoCorrect: true` and `AutoCorrect: true`Use RuboCop 1.17.1+Use RuboCop Performance 1.17Make `Metrics/ClassLength` aware of singleton classMerge pull request #11775 from koic/make_style_trailing_body_on_class_aware_of_singleton_classMake `Style/TrailingBodyOnClass` aware of singleton classMake `Style/ClassStructure` aware of singleton classFix typos[Fix #11765] Fix an error for `Style/MultilineMethodSignature`Merge pull request #11769 from ydah/style-file-empty-only-safe-falseRemove redundant `SafeAutoCorrect: false`Rake task: Handle missing docs folder / TOC fileRake task: Extract a `docs_path` variableUse preferred methods instead deprecated methods for `AST::ProcessedSource`[Fix #11762] Fix an incorrect autocorrect for `Style/ClassEqualityComparison`[Fix #11758] Fix a false positive for `Style/RedundantLineContinuation`Merge pull request #11752 from koic/fix_a_false_positive_for_style_redundant_line_continuationFix a false positive for `Style/RedundantLineContinuation`Merge pull request #11754 from ydah/fix-false-positive-for-RedundantLineContinuationFix a false positive for `Style/RedundantLineContinuation` when using `&&` and `||` with a multiline condition.Add new `Lint/DuplicateMatchPattern` copMove a changelog entryAdd missing changes to the changelog and the release notes (#11751)Switch back the docs versionDepfu 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