-
Notifications
You must be signed in to change notification settings - Fork 134
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
validate against ambiguous references #1372
validate against ambiguous references #1372
Conversation
if (classSymbol == null) { | ||
return false; | ||
} | ||
Set<Symbol.MethodSymbol> matching = ASTHelpers.findMatchingMethods( |
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.
this is a super cool helper method! didn't know it existed
import org.junit.jupiter.api.Test; | ||
|
||
public class LambdaMethodReferenceTest { | ||
|
||
private CompilationTestHelper compilationHelper; | ||
private RefactoringValidator refactoringValidator; | ||
private CompilationTestHelper compile() { |
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.
gotta keep those tests fast 😛
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.
heh, most of our tests are structured this way so I moved it over. I think I migrated most of them after hitting a few cases where tests flaked after helper/validator instances were reused (due to either parallelism or multiple asserts in a single test). This way they're always clean regardless of other state!
There's one more bug that I'm aware of where we trasform |
Before this PR
After this PR
==COMMIT_MSG==
==COMMIT_MSG==
Possible downsides?