-
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 likely static import clash with FailWithMessage{,AndThrowable}
Refaster rules
#939
Prevent likely static import clash with FailWithMessage{,AndThrowable}
Refaster rules
#939
Conversation
Looks good. No mutations were possible for these changes. |
88df557
to
ebb06f4
Compare
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.
LGTM 👍
// https://github.com/google/error-prone/pull/3584 is resolved. Until that time, statically | ||
// importing AssertJ's `fail` is likely to clash with an existing static import of JUnit's | ||
// `fail`. Note that combining Error Prone's `RemoveUnusedImports` and | ||
// `UnnecessarilyFullyQualified` checks and our `StaticImport` check will anyway cause the |
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 was worried about the order of checks and potential clashes still, but luckily the StaticImport
check guards against that.
…e}` Refaster rules This is a workaround for google/error-prone#3584. While there, drop an unused method from `JUnitToAssertJRules`.
ebb06f4
to
96c3c20
Compare
Looks good. No mutations were possible for these changes. |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
FailWithMessage{,AndThrowable}
Refaster rulesFailWithMessage{,AndThrowable}
Refaster rules
This resolves an issue observed internally.
Suggested commit message:
(It'd be better to fix google/error-prone#3584, but that looks to be (very) complicated; no time for that right now.)