Skip to content
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

Handle SuggestedFixes#qualifyStaticImport method declaration clashes #2009

Conversation

Stephan202
Copy link
Contributor

If a class declares a method m then statically importing another method m does not have the desired effect.

If a class declares a method `m` then statically importing another
method `m` does not have the desired effect.
@google-cla google-cla bot added the cla: yes label Dec 13, 2020
}

@Test
public void qualifyStaticImport_whenMethodNamesClash_usesQualifiedName() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prior to these changes this test would fail, because verifyNotNull is declared but not referenced.

@Stephan202 Stephan202 deleted the bugfix/SuggestedFixes-qualifyStaticImport-check-method-declarations branch December 15, 2020 20:58
stevie400 pushed a commit to HubSpot/error-prone that referenced this pull request Jan 15, 2021
If a class declares a method `m` then statically importing another method `m` does not have the desired effect.

Fixes google#2009

COPYBARA_INTEGRATE_REVIEW=google#2009 from PicnicSupermarket:bugfix/SuggestedFixes-qualifyStaticImport-check-method-declarations 96279a5
PiperOrigin-RevId: 347673530
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants