-
Notifications
You must be signed in to change notification settings - Fork 39
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
Prevent ReverseOrder
Refaster rule from introducing a static import
#397
Conversation
Looks good. No mutations were possible for these changes. |
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 for the quick turn around and fixing this!
W.r.t. suggested commit message made one tweak.
... in that case we need another tweak (applied it). |
@Stephan202 shouldn't it be both "check"? |
This is a workaround for the issue resolved by google/error-prone#3584. After application of this Refaster rule, any static imports of `java.util.Collections.reverseOrder` are obsolete. These can be removed by running Google Java Format or Error Prone's `RemoveUnusedImports` check. Where possible, subsequent application of the `StaticImport` checker will statically import `java.util.Comparator.reverseOrder`.
2e411c2
to
f9b309f
Compare
Rebased. |
Looks good. No mutations were possible for these changes. |
Doh, I misread the diff. I'm fine either way (I also prefer |
This is a workaround for google/error-prone#3584.
Suggested commit message: