-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Checkstyle assign on same line #8601
Checkstyle assign on same line #8601
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, except for the unused code removal. Thanks ;-)
@@ -18,159 +18,13 @@ | |||
|
|||
package org.schabi.newpipe.util.urlfinder; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think you can just remove things from this file at random. This file was taken from AOSP and modified, as the licence explains (though a comment would be better), so any change should be documented I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes should already be documented by git
(git blame, commit, etc).
Therefore I don't think further action is required as the first line /* THIS FILE WAS MODIFIED, CHANGES ARE DOCUMENTED. */
already describes this.
I added an
//!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// CHANGED: Removed unused code //
//!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
block so that we are completely on the safe side.
02f836c
to
fc7fe67
Compare
So that the assign operators are used on the same branch
+ Removed some unused code
fc7fe67
to
3ba04f1
Compare
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks :-)
What is it?
Description of the changes in your PR
See #8170 (comment).
After some discussion with @Stypox a while ago (can't find the issue/PR anymore :/ ) where to put the
=
on a new line or not we agreed to put it not on the next line.This PR was create to enforce this behavior.
This PR also removes some unused code that was found on the fly.
After the PR is merged the changes should also be applied to https://github.com/TeamNewPipe/NewPipeExtractor
Due diligence